DxTx for EHR · SMART on FHIR
DxTx calculators, opened from the patient record. The values a calculator needs are read from the chart, the clinician reviews them, and the result appears without re-keying.
For health systems and practices: DxTx connects through the open SMART App Launch standard, with read-only access limited to the patient in view. We welcome inquiries from organizations interested in piloting it.
Standard
SMART on FHIR
HL7® FHIR® R4 · SMART App Launch
Access
Read-only
Limited to the patient in view. Nothing is written to the chart.
Patient data stored
None
In the current release, the calculation runs in the clinician’s browser.
A clinician opens DxTx from the patient record through the SMART App Launch protocol. The EHR passes the patient in context, so there is no separate login and no patient search.
Each calculator reads only the chart values it needs. Every pre-filled value is shown with its measurement date and stays editable, and old or missing values are flagged, so the clinician confirms the inputs before reading the result.
If a value is not on file, or cannot be read, the calculator says so and accepts manual entry. The calculation is the same one used on the DxTx website.
What DxTx reads today
DxTx reads only what each calculator needs, with your organization’s approval, and never writes back to the chart.
What DxTx does not do
If a future feature needs to store data, it will be documented on this page and agreed with each organization before it is enabled.
DxTx for EHR is a SMART on FHIR application built on HL7 FHIR R4. It uses the SMART App Launch protocol for sign-in and patient context, and requests read-only access limited to the patient in view. The permissions it requests are listed in the app registration, where your security team can review them.
SMART App Launch is an open standard supported by the major EHR systems. We confirm compatibility with each EHR by testing in that vendor’s sandbox, and then in your own test environment, before any site goes live.
We confirm which EHR you run, that it supports SMART App Launch, and which calculators your clinicians want.
We provide documentation of the data elements read and the permissions requested, for your organization’s review.
Your team enables DxTx in a non-production environment. We check the pre-filled fields against how your record is coded.
A small group of clinicians uses DxTx from live charts, and we adjust based on what they find.
Production launch for your organization.
Timelines depend on your organization’s review process. We agree one with you in the scoping call.
DxTx connects through SMART on FHIR wherever the chart exposes it, and that work travels: one app registration covers Epic sites from Wisconsin to Lucerne to Singapore. We open new integration conversations every week across these markets. Choose your country or region for the systems we connect to there and how to start.
The systems. Epic, Oracle Health, athenahealth, MEDITECH Expanse, NextGen Healthcare and eClinicalWorks — certified US EHRs ship the SMART App Launch door DxTx uses.
The DxTx route. Compatibility is confirmed in the vendor’s sandbox, then in your test environment, then pilot and go-live — the steps above, unchanged.
Language. English interface and content. SI and conventional units both accepted, with one-tap conversion in every calculator.
Request integrationThe systems. Epic and Oracle Health at a growing set of NHS trusts, System C and others.
The DxTx route. Your trust’s EPR. DxTx is clinician-facing inside the chart — we are deliberately not another portal. Where your trust runs Epic or Oracle Health, our existing build applies directly, and we work within your trust’s standard procurement frameworks.
Language. English interface and content.
Request integrationThe systems. ChipSoft HiX in most hospitals; Epic at the large academic centers, Radboudumc among them.
The DxTx route. Epic sites use the same app registration as our US build, with localization reviewed per site. For HiX we scope against the FHIR capability your configuration exposes — in test first, as always. MedMij does not apply to a clinician-facing launch inside the EPR, which keeps the paperwork where it belongs.
Language. English interface today; Dutch localization is scoped as part of your integration request.
Request integrationThe systems. Epic, with its country packs — FMK and MedCom in Denmark — and TietoEvry across the region.
The DxTx route. Epic sites: the same app registration as our US build. A calculator that reads medications meets FMK-sourced data in Denmark, and we verify that mapping in your test environment, not in production. TietoEvry and other regional systems: per-site scoping.
Language. English interface today; Danish, Swedish, Norwegian or Finnish localization is scoped per market with your request.
Request integrationThe systems. Dedalus (ORBIS) in hospitals, with gematik’s rails underneath: ISiK is making inpatient data addressable over FHIR R4, and the ePA now covers most of the statutorily insured.
The DxTx route. Where your system exposes FHIR R4, DxTx launches as it does elsewhere, scoped per site. On the ePA rail we take the third-party read path — DxTx never writes, so the DiGA route is a process we simply do not need.
Language. English interface today; German localization is scoped as part of your integration request.
Request integrationThe systems. Epic at Luzerner Kantonsspital and Insel Gruppe, among others.
The DxTx route. Epic sites: the existing app registration, localization reviewed per site. The EPD is document exchange, not a live clinical API — the working route into the chart is the hospital’s own EPR, and that is where DxTx connects.
Language. English interface today; German, French or Italian localization is scoped per site.
Request integrationThe systems. Dedalus strongest in France, Germany and Italy; national champions elsewhere. We scope per site against the FHIR surface the installed system exposes, tested on vendor-neutral SMART tooling before we touch your environment.
Language. English interface today; localization is scoped per market with your request.
Request integrationThe rails. The Ayushman Bharat Digital Mission (ABDM) — an open, FHIR-aligned national layer, past one billion linked health records.
The DxTx route. Our read-only model maps directly onto ABDM’s consent-based HIU pattern, and where a hospital runs a SMART-capable EHR we launch from the chart as elsewhere. We confirm what your facility’s APIs actually support before quoting a timeline — not after.
Language. English interface — the working language of Indian clinical software.
Request integrationThe systems. Epic covers Singapore’s entire public hospital system — our existing Epic build applies directly. Large South Korean and Southeast Asian systems (ezCaretech, IQVIA and others): per-site scoping.
Language. English interface — Singapore’s clinical working language; other markets scoped per request.
Request integrationThe systems. Many of the region’s flagship systems run Epic or Oracle Health — where they do, our existing SMART on FHIR build applies directly.
The DxTx route. A scoping call, the vendor sandbox we have already cleared, then your test environment.
Language. English interface, as in most of the region’s clinical systems.
Request integrationThe systems. Both markets run on domestic platforms — Fujitsu and Wemex in Japan, Winning Health and Neusoft in China — without an open SMART on FHIR door today.
The DxTx route. These doors open when an institution asks its vendor. If your institution wants DxTx, write to us — we will tell you plainly what is workable.
Start the conversationDxTx is published in English — the language of the source literature its calculators are built from. Local-language interfaces are scoped market by market as part of an integration request: tell us what your clinicians need and it goes in the plan, not the brochure.
Unit handling is already local everywhere. Calculators accept SI and conventional units with one-tap conversion — µmol/L or mg/dL, mmol/L or mg/dL — so a Copenhagen chemistry panel and a Chicago one land in the same calculator without re-keying arithmetic.
DxTx presents validated, referenced calculators to healthcare professionals and writes nothing to the chart. Software rules differ by market, so classification questions are assessed with your team during scoping — not discovered after go-live.
Email support@orakleinc.com with the EHR you run and roughly how many clinicians would use it. We will reply to arrange a scoping call. We open multiple new integration conversations each week, so please allow a short lead time for the call — we like to come prepared.
Email support@orakleinc.comQuestions about security, permissions or data handling? Ask the team directly.
Educational use by healthcare professionals. Not a substitute for clinical judgement or individual assessment. HL7® and FHIR® are the registered trademarks of Health Level Seven International; their use does not constitute an endorsement by HL7.
Cookies. We use Google Analytics to understand how DxTx is used. It sets cookies only if you accept. Privacy Policy