HL7 FHIR R4Electronic Medical Records

What Is FHIR? The Standard Behind Modern Electronic Medical Records

HL7 FHIR (Fast Healthcare Interoperability Resources) R4 is the global standard for representing and exchanging electronic health records. DrGodly uses FHIR natively — every patient record, appointment, observation, and clinical encounter is a structured, interoperable FHIR resource.

Explore FHIR Resources

HL7 FHIR R4

Global Standard

Resources Used

REST + GraphQL

API Format

HIPAA Aligned

Compliance

FHIR Resources

The Seven Core FHIR Resources in DrGodly

Each clinical concept — from a patient registration to a completed consultation — maps to a dedicated, standardized FHIR R4 resource.

Patient

FHIR R4 Resource

Stores patient demographics, contact information, identifiers, and communication preferences. The anchor resource every clinical record links back to.

namebirthDategenderaddresstelecomidentifier

Practitioner

FHIR R4 Resource

Clinician profiles with qualifications, specialties, and contact details. Used to link practitioners to appointments and encounters.

namequalificationspecialtytelecomaddress

Appointment

FHIR R4 Resource

Represents a scheduled clinical interaction between patient and practitioner. Status codes: booked, arrived, fulfilled, cancelled, no-show.

statusstartendparticipantserviceTypedescription

Encounter

FHIR R4 Resource

Created at consultation completion. Captures the full clinical encounter: SOAP notes, AI summary, diagnosis, and treatment plan.

statusclasssubjectparticipantperiodreasonCode

Observation

FHIR R4 Resource

AI-extracted clinical observations from patient intake — vitals, symptoms, severity scores, and structured clinical findings.

statuscodesubjectvalue[x]effectiveDateTimeinterpretation

Condition

FHIR R4 Resource

Diagnoses and health conditions linked to SNOMED CT terminology. Created from AI differential diagnosis and clinician review.

clinicalStatuscodesubjectonsetDateTimeevidenceseverity

DocumentReference

FHIR R4 Resource

Clinical documents including intake reports, consultation summaries, discharge notes, and AI-generated clinical reports.

statustypesubjectdateauthorcontent

Clinical Mapping

Every Clinical Action Creates a FHIR Record

DrGodly does not store clinical data in proprietary tables and convert it later. Every user action — booking, intake, consultation, diagnosis — writes directly to the corresponding FHIR resource in real time.

Patient books appointmentAppointment

AI intake collects symptomsObservation

AI extracts diagnosis hintsCondition

Doctor consults patientEncounter

Clinical report generatedDocumentReference

Sample FHIR ObservationR4

resourceType:"Observation"

status:"final"

code.text:"Chief Complaint"

valueString:"Persistent headache, 3 days"

subject.ref:"Patient/PAT-00241"

effectiveDateTime:"2026-06-16T10:30:00Z"

interpretation:"moderate severity"

FHIR R4 vs. Legacy Proprietary EMR

Aspect	DrGodly — FHIR R4 Native	Legacy Proprietary EMR
Data Format	Structured JSON/XML resources with standardized fields	Proprietary database schemas — different per vendor
Interoperability	Any FHIR-compatible system can read and write your records	Requires expensive middleware or manual data exports
AI Integration	AI tools query FHIR resources directly via structured APIs	AI must parse unstructured text or fragile CSV exports
Compliance	HIPAA-aligned resource types with built-in PHI boundaries	Compliance mapping requires costly integration projects
Extensibility	Open ecosystem of FHIR profiles, IGs, and implementations	Closed vendor roadmaps, locked behind contract terms

Ready to Run on a FHIR-Native EMR?

Start building on a platform where every patient record is a proper FHIR R4 resource — interoperable, secure, and AI-ready from day one.