A per-tenant Business Central (AL) extension that adds patient and encounter records, a service/procedure catalog, insurance claim and co-pay billing, batch/expiry pharmacy inventory, and department-level cost centers — built, installed and supported by ECOSIRE on your environment. Built to order by ECOSIRE for Dynamics 365 BC (build-to-order) — indicative price from $499.00 USD; request a quote for a scoped proposal.
Manifeste de l'app
Conçu autour de votre flux de travail
A per-tenant Business Central (AL) extension that adds patient and encounter records, a service/procedure catalog, insurance claim and co-pay billing, batch/expiry pharmacy inventory, and department-level cost centers — built, installed and supported by ECOSIRE on your environment.
Aucune configuration à faire vous-même — une app fonctionnelle conçue, installée et prise en charge par ECOSIRE.
Commencez par un prix de développement unique. Nous cadrons le projet avec vous au lancement.
ECOSIRE la développe, la configure et l'installe sur votre Dynamics 365 Business Central.
Vous êtes en ligne en 2–4 semaines environ, avec une période d’assistance après le lancement.
Clinics and hospitals run on Business Central for finance and inventory, but core BC has no concept of a patient, an encounter, an insurance claim, or a drug batch nearing expiry. Teams end up patching those gaps with spreadsheets and a disconnected practice-management tool that never reconciles back to the general ledger.
Healthcare Clinic & Hospital Management closes that gap as a native AL extension installed directly on your Business Central tenant. It adds patient and encounter master tables, a service and procedure catalog with payer-aware pricing, an insurance claim and co-pay billing engine, pharmacy and medical inventory tracked by lot/batch and expiry, and department-level cost centers mapped to BC dimensions — so clinical activity posts straight into your existing chart of accounts.
This is build-to-order, not an instant AppSource download. After purchase, ECOSIRE scopes your payer mix, service catalog, departments and posting rules, then builds the extension using table and page extensions, event subscribers and the BC REST/OData v4 API. We deploy it as a per-tenant extension to your sandbox first, validate billing and claim flows with your finance team, then publish to production. Permission sets scope clinical, pharmacy and billing roles; the BC job queue runs recurring claim batches and expiry alerts.
The build typically lands in 3 to 5 weeks depending on payer and catalog complexity. Because it lives inside Business Central, patient invoices, claim receivables, pharmacy stock and department P&L all stay in one ledger — no nightly imports, no reconciliation drift. ECOSIRE provides the source AL, documentation, and ongoing support and version compatibility as Microsoft ships BC updates.
Owns the P&L and wants clinical activity, payer receivables and pharmacy stock posting into one Business Central ledger with department-level visibility — no spreadsheet reconciliation between a separate practice system and the GL.
Manages claim submission, denials and co-pay collection. Needs each encounter split cleanly into payer and patient portions, claim status tracked end to end, and receivables landing against the correct payer customer.
Responsible for medical inventory and dispensing. Relies on lot/batch and expiry tracking, FEFO picking and automated expiry alerts to cut wastage and stay compliant on controlled-stock handling.
| Critère | ÉCOSIRE | Construction personnalisée | Concurrent | Odoo natif |
|---|---|---|---|---|
| Patient billing & claims posted natively into the BC general ledger | Inclus | Prise en charge partielle | Prise en charge partielle | |
| Pharmacy inventory with lot/batch + expiry (FEFO) tracking | Inclus | Prise en charge partielle | Prise en charge partielle | |
| Built, installed and supported on your tenant as a per-tenant extension | Inclus | Inclus | Non inclus | |
| Configured to your payer mix, catalog and departments out of the box | Inclus | Prise en charge partielle | Non inclus | |
| Full AL source code handed over to you | Inclus | Inclus | Non inclus | |
| Ongoing BC version-compatibility maintenance included | Inclus | Non inclus | Prise en charge partielle | |
| Predictable one-time build cost without a full in-house AL dev team | Inclus | Non inclus | Prise en charge partielle |
No. This is a build-to-order extension. After purchase, ECOSIRE scopes your payers, service catalog, departments and posting rules, then builds and installs the app as a per-tenant extension directly on your Business Central environment. There is no public AppSource listing to download — you get a solution configured for your tenant, not a generic one.
Typically 3 to 5 weeks from kickoff. Simple single-clinic, single-payer setups land at the shorter end; multi-department hospitals with several insurers and contracted-rate matrices take longer. We deploy to your sandbox first, validate billing and claim flows with your finance team, then publish to production on an agreed date.
Your purchase includes a post-go-live support window plus ongoing BC version-compatibility maintenance. Microsoft ships Business Central updates roughly twice a year; ECOSIRE keeps the extension compatible across those cycles. You also receive the full AL source code and documentation, so you are never locked out of your own solution. Extended support and enhancement plans are available separately.
Yes. The extension uses BC's native posting routines and dimensions. Patient invoices, co-pays and claim receivables post as standard sales documents, pharmacy stock uses standard item ledger entries, and each department maps to a BC dimension so revenue and cost flow into your existing chart of accounts without imports or middleware.
Yes. The service and procedure catalog resolves pricing per payer — list price, each insurer's contracted rate, and self-pay rates. At billing time each encounter is split into the payer claim and the patient co-pay using the resolved rates, and claim receivables post against the correct payer customer record.
Yes. The extension exposes patients, encounters and claims through the Business Central REST/OData v4 API, and can optionally integrate with Dataverse and the Power Platform. That lets you connect lab systems, build Power Apps front-desk capture, automate claim-status notifications with Power Automate, or report directly in Power BI.
A per-tenant Business Central (AL) extension that adds patient and encounter records, a service/procedure catalog, insurance claim and co-pay billing, batch/expiry pharmacy inventory, and department-level cost centers — built, installed and supported by ECOSIRE on your environment.