MedAppz reads a patient out as FHIR R4, with everything on their record, and exports the whole practice as bulk FHIR. It works today with an API key your clinic creates itself, scoped to FHIR read.
Patient/{id} returns one FHIR Patient, and Patient/{id}/$everything returns their encounters, observations, conditions, allergies, prescriptions, reports and documents.
The bulk $export writes NDJSON, one file per resource type, started with a key and collected when it is ready.
FHIR Link shows its mapping element by element, naming the column each field comes from.
A bundle can be taken in against a patient you already hold, with every validation finding kept against its FHIR path.
Every exchange is logged, failed ones too. A key can read under FHIR and never write.
Switching it on
What it takes
1Step 1Create an API key with the FHIR read scope in MedAppz.
2Step 2Read the capability statement at the FHIR metadata address to see what is supported.
3Step 3Call the FHIR endpoints with the key as a bearer token.
What it does not do yet
A FHIR key reads every patient in the practice, so only the owner should issue one. Where FHIR expects a terminology this deployment has not loaded, the value travels in MedAppz’s own codes and the exchange says so.
Yes. It works on medappz.com today. MedAppz reads a patient out as FHIR R4, with everything on their record, and exports the whole practice as bulk FHIR. It works today with an API key your clinic creates itself, scoped to FHIR read.
How do I switch on FHIR R4?
Create an API key with the FHIR read scope in MedAppz. Read the capability statement at the FHIR metadata address to see what is supported. Call the FHIR endpoints with the key as a bearer token.
What does the FHIR R4 connection not do yet?
A FHIR key reads every patient in the practice, so only the owner should issue one. Where FHIR expects a terminology this deployment has not loaded, the value travels in MedAppz’s own codes and the exchange says so.