Fast Healthcare Interoperability Resources is the standard on which clinical data exchange now converges. Adopting it means BAEMS can exchange with an electronic health record, a laboratory system or national digital health infrastructure without a custom interface for each.
These fifteen resources cover the emergency care pathway from arrival through diagnosis and treatment to reimbursement.
- Patient
- An individual receiving or awaiting care — demographics, history and contact details. The anchor resource for everything else.
- Encounter
- An interaction between patient and provider: location, date, reason and the parties involved.
- Condition
- A clinical condition, problem or diagnosis, with onset, severity, status and clinical notes.
- Observation
- Clinical observations and measurements — vital signs, laboratory results, diagnostic readings.
- Procedure
- A procedure performed on a patient: type, date and time, performer, outcome.
- MedicationRequest
- A request for medication with name, dosage, frequency and instructions.
- MedicationAdministration
- The actual administration of a medication: what, how much, by what route, at what time.
- AllergyIntolerance
- A patient's allergy or intolerance — allergen, reaction, severity, onset. Critical in unconscious presentation.
- DiagnosticReport
- A report of diagnostic tests or imaging: type, results, interpretation and conclusion.
- Immunisation
- Immunisation history — vaccine, date, dosage and provider.
- Location
- A physical location where care is delivered: name, address, type and contact.
- Practitioner
- An individual provider involved in care: name, role, specialty, contact.
- Organisation
- An organisation delivering care: name, type, address and contact.
- Coverage
- Insurance coverage or benefit plan — type, policy holder, effective dates. The PM-JAY linkage point.
- Claim
- A request for reimbursement: service codes, costs and payer information.
Delivery
Implementation timeline
| Phase | Duration | Activity |
|---|---|---|
| Analysis and requirements | 2–4 weeks | Assess existing data systems and workflows; identify the FHIR resources needed for interoperability with external systems. |
| System design and architecture | 4–6 weeks | Design FHIR APIs and data models; define integration points and communication protocols. |
| Development and integration | 8–12 weeks | Develop FHIR APIs and data interfaces; integrate FHIR capability into BAEMS backend systems and databases. |
| Testing and validation | 4–6 weeks | Unit, integration and interoperability testing; validate exchange with external healthcare systems. |
| Deployment and go-live | 2–4 weeks | Deploy to production; user training and rollout to stakeholders. |
Resources required
FHIR integration specialist, backend developers, database administrators, quality assurance engineers, and a project manager.