1. Where each part stands
| Part | Status |
|---|---|
| Ordering from the chart | Coming soon. QDX Lab Ordering is a provider app on ModMed's FHIR API; ask us about being among the first practices to use it. |
| Results into the ModMed chart | Not yet. ModMed's certified FHIR API is read-only; writing results needs ModMed's paid API or an HL7 lab interface, arranged when your practice comes on board. |
| Results meanwhile | By fax into your ModMed fax inbox, or any other way you choose in QDX. See Results into any EMR by fax. |
2. The ordering app
| Setting | Value |
|---|---|
| App | QDX Lab Ordering: provider app, public client with PKCE (S256), FHIR R4 |
| Launch and redirect URL | https://qdx.systems/app/launch.html |
| What it reads | openid fhirUser launch user/Patient.rs user/Practitioner.rs user/Encounter.rs user/Condition.rs. It writes nothing. |
| How it reaches your chart | ModMed places a link to the app inside your EMA after a provider at your practice first signs in to it, per ModMed's documentation for certified apps. |
How QDX knows it is your practice: ModMed gives each practice its own FHIR address (for example https://yourpractice.mmi.prod.fhir.ema-api.com/fhir/r4). QDX matches that address to your QDX organization only after QDX has confirmed it with you.
3. In QDX
Your QDX administrator adds the connection under Settings > EMR connections: ModMed, your practice's FHIR address (listed at ModMed's public endpoint directory), the client ID QDX gives you, and test or live mode. QDX then confirms the practice with you before launches connect.
4. Questions
Write to ops@qdx.systems.