Represents unverified clinical information reported by a caller or dispatcher before physical patient assessment by an emergency medical practitioner.

Caller-reported observations must remain distinct from observations recorded after direct clinical assessment.

Represents a patient's allergy or intolerance recorded during Kenya emergency medical services and facility workflows.

Criticality and reaction detail are must-fetch on patient lookup and must never be silently dropped. By the time the allergy-history section of an assessment is marked complete, the patient must have either one or more EMAllergyIntolerance instances with a real allergen code, or exactly one EMNoKnownAllergy instance — never both, never neither.

An explicit record asserting that a full allergy history was taken and nothing was found, distinct from simply having zero AllergyIntolerance resources.

The absence of any AllergyIntolerance resource is ambiguous — it could mean 'confirmed none' or 'never asked' — and that ambiguity is exactly the kind of gap that can lead to a contraindicated drug being administered.

Kenya Case Assessment profile representing structured clinical assessments.

Represents the complete emergency department patient chart as a single document, mirroring the WHO-adapted Emergency Department Patient Record paper form: a fixed section list, each referencing the relevant clinical resource instances captured during the encounter.

History of Present Illness, Trauma narrative, Management Plan, Final Reassessment comment, Additional Notes, and Nursing Progress Notes are captured as section narrative text (section.text) rather than as separate resource types — these are free-text-only fields on the source form with no checkbox/coded structure to model.

Kenya Composition profile representing a clinical or administrative entry composition.

A specialization of Condition for emergency diagnosis staging. Do not reuse this profile for a generic/routine-visit Condition.

One emergency encounter (EMIncidentEncounter/EMPOCEncounter/EMEDEncounter) is expected to produce multiple Condition instances over time — one per diagnostic stage — distinguished by category and verificationStatus, and never overwritten in place: chief-complaint (minimum 1), past-medical-history (0.., pre-existing comorbidities captured during intake rather than staged diagnoses of this presentation), working-diagnosis or differential-diagnosis (0..), and discharge-diagnosis (0..*, required before the encounter can be considered diagnostically closed for claims purposes, though that is an encounter-closure business rule rather than a FHIR cardinality constraint on this profile).

Represents an emergency investigation result, e.g. a 12-lead ECG, laboratory result, or imaging report, generated during pre-hospital or facility-based emergency care.

Kenya DocumentReference profile for clinical and administrative documents.

Represents the facility-based emergency department encounter, from registration and triage through provider assessment, treatment, and disposition.

Distinct from EMIncidentEncounter (dispatch/field response) and EMPOCEncounter (pre-hospital point-of-care care): this profile represents the receiving facility's own chart, adapted from the WHO Emergency Unit Patient Record form. When the patient arrived by EMS, link back to the pre-hospital chain through partOf rather than duplicating dispatch/field data here.

Represents the complete emergency medical services incident from dispatch initiation through handover at the receiving facility.

This Encounter is the root encounter for an EMS episode. It captures dispatch information, the reporting caller, the dispatcher, responding units, participating emergency agencies, scene information, and the destination facility.

Clinical care performed by the responding emergency team should be represented using a separate point-of-care Encounter whose partOf element references this Encounter.

Represents the direct patient-care encounter performed by an emergency medical team at the scene or during transport.

The point-of-care Encounter is subordinate to the root emergency incident Encounter and references it through Encounter.partOf.

A prominent, must-see alert referencing a high-criticality EMAllergyIntolerance record.

Reuses the base FHIR Flag resource, designed exactly for prominent alerts, rather than requiring every consuming system to know a local convention on AllergyIntolerance. Intended for use specifically with EMAllergyIntolerance instances where criticality = high.

Encounter profile for ambulance services in Kenya.

Represents the physical healthcare facility or emergency-care location intended to receive, or that actually received, a patient transported by emergency medical services.

The Location identifies the physical destination. The organization operating the facility is referenced through Location.managingOrganization.

Represents the physical location at which an emergency incident occurred or at which the patient was found.

The location supports coordinates, landmarks, descriptive directions, and administrative geographic details.

Represents the real-time geographic position and response status of an emergency responder unit, referenced from EMResponderUnit.location.

Represents a medication administered to a patient during Kenya emergency medical services and facility clinical workflows.

Used instead of MedicationRequest because emergency care is administration-heavy — drugs are given in real time, not merely prescribed.

Represents whether active bleeding was reported by the caller or dispatcher before direct clinical assessment.

Represents the patient's apparent breathing status as reported by a caller or dispatcher before direct clinical assessment.

Represents the patient's apparent level of consciousness as reported by the caller or dispatcher before direct clinical assessment.

Represents the provider's structured resuscitation assessment of a single ABCDE letter (Airway, Breathing, Circulation, Disability, or Exposure) — one Observation instance per letter, not one Observation for the whole ABCDE assessment, mirroring the one-instance-per-region pattern already used by EMSecondarySurveyObservation.

Reuses the same explicit "NML" (no findings) idiom as EMSecondarySurveyObservation via the EMNoFindingsOnExam extension. Which component slices are populated depends on Observation.code: airway, breathing, and exposure typically populate only a few of the fields below, while circulation and disability are the most component-heavy. Airway, breathing, and circulation interventions performed (repositioning, suction, OPA/NPA/BVM/LMA/ETT, chest tube, IV line placement) are recorded as EMProcedure instances referenced separately, not duplicated here; medications and blood products given are recorded as EMMedicationAdministration.

Represents the WHO Emergency Unit high-risk-signs checklist performed at triage: a single Observation per triage event carrying one boolean component per high-risk sign, plus a top-level summary flag for whether any sign is present.

Represents a single point-of-care ultrasound view (abdomen/FAST, chest, or cardiac) performed during the ED assessment — one Observation instance per view. The trace/clip image itself, if transmitted, belongs on the referencing EMDiagnosticReport.presentedForm rather than on this Observation.

Represents the ED provider's physical examination of a single body system/region — one Observation instance per system, not one Observation for the whole exam. Distinct from EMSecondarySurveyObservation, which represents the pre-hospital secondary survey (a different clinical event, performed earlier, organized by EMS body region rather than by ED exam system); kept as a separate profile rather than widening EMSecondarySurveyObservation's region value set. Reuses the same explicit "NML" idiom via EMNoFindingsOnExam.

Represents the review of a single body system during the ED provider assessment — one Observation instance per system, not one Observation for the whole review of systems. Reuses the same explicit "NML" idiom as EMSecondarySurveyObservation and EMABCDEAssessmentObservation via the EMNoFindingsOnExam extension.

Represents the examination of a single body region during an emergency secondary survey — one Observation instance per body region examined (head, neck, chest, back-and-spine, abdomen, pelvis, upper-extremities, lower-extremities), not one Observation for the whole secondary survey.

Mirrors the explicit-absence pattern used on EMAllergyIntolerance: a region with nothing abnormal found must be recorded as an explicit "examined, no findings" Observation, never left as a silently-missing resource. A full-body exam is expected to produce exactly 8 Observation instances (fewer only if the survey was genuinely partial, e.g. limited by scene safety) — that expectation is a workflow-completeness rule, not a FHIR structural constraint on this profile.

A standalone, trendable triage acuity record, separate from EMIncidentEncounter.priority (dispatch) and EMPOCEncounter.priority (on-scene).

Only create this Observation when the workflow needs acuity trending as discrete timestamped events; if a single current-priority value per encounter is sufficient, Encounter.priority alone is enough and this Observation is unnecessary.

Represents a urine dipstick panel performed during the ED assessment, one component per analyte (glucose, ketones, blood, nitrite, leukocytes, protein).

Represents a single vital-sign measurement (heart rate, respiratory rate, temperature, SpO2, blood pressure, or Glasgow Coma Scale) captured during Kenya emergency medical services and point-of-care workflows.

Largely reuses the standard FHIR vital-signs pattern rather than inventing new structure. One Observation instance is created per measurement, per reading time, so trends across the episode (dispatch snapshot, on-scene, in-transit, ED arrival) can be reconstructed.

Represents a patient receiving pre-hospital or emergency services in Kenya.

The profile supports identified and unidentified patients, temporary emergency tracking, identity verification, minimal emergency demographics, and reconciliation of temporary Patient records with verified Patient records.

Represents a clinical procedure performed during Kenya emergency medical services and point-of-care workflows, e.g. CPR, endotracheal intubation, wound dressing, or splinting.

Kenya QuestionnaireResponse profile representing captured questionnaire responses.

The detailed lifecycle status of a Kenya ambulance case, using the Kenya-specific status codes that do not map one-to-one onto the base FHIR Encounter.status ValueSet.

Describes whether a destination facility provides emergency-care services and the level of emergency capability available.

Auto-generated clinical guidance text tied to an observation's severity flag, e.g. instructions to start supplemental oxygen and reassess airway and breathing.

How the patient arrived at the emergency department.

Supplementary detail for the ED encounter disposition that does not fit Encounter.hospitalization.dischargeDisposition alone — the discharge-plan discussion flag, and the reason text for the leave-without-being-seen, death, and transfer dispositions.

Patient's mobility status recorded at emergency department registration, independent of triage acuity.

Payment method recorded at emergency department registration.

Whether the presenting problem is acute or chronic, recorded at registration.

Whether the patient was referred to the emergency department, e.g. from another facility or a clinic.

Mechanism, intent, timing, and recent substance use for a trauma presentation.

Represents the Kenya health-system level assigned to a receiving healthcare facility.

Captures the person who reported the emergency incident.

The caller may be the Patient, a person related to the Patient, or an unlinked person such as a bystander. This extension is necessary because the base Encounter.participant.individual element does not permit Patient or Person references in FHIR R4/R4B.

Number of attempts made to administer a medication, relevant for repeated-dose protocols and difficult-access scenarios.

Explicit flag confirming that a body region was examined and that nothing abnormal was found.

Indicates whether the patient is considered an adult during emergency assessment or triage.

Represents the patient's estimated age when the exact date of birth is unknown or has not been verified.

Indicates whether the patient's identity has been verified through an appropriate identification or verification process.

Represents a practitioner or practitioner role assigned to an emergency responder unit.

The extension records both the assigned person or role and their operational crew function.

Date and time the responder unit's geographic position was last refreshed.

Ownership category of the organization operating an emergency responder unit, e.g. government, private, or NGO.

Indicates whether a responder unit has been stood down or replaced by another unit during the incident.

The responder unit's current response state, e.g. dispatched, en-route, on-scene, transporting, or at-facility.

Identifier of the onboard telematics or tracking device fitted to an emergency responder unit, if present.

References an ambulance or other emergency-response vehicle assigned to the incident.

References another emergency-response organization participating in the incident, such as fire services, police, security services, or disaster management services.

Indicates whether the Patient resource represents an individual whose identity has not yet been established.

Age-group bucket used to select the applicable reference range for a vital-sign reading, e.g. adult versus paediatric.

Qualitative descriptor of a vital-sign reading, independent of its numeric value, e.g. a pulse described as weak or a breathing pattern described as labored.

Dispatcher-assigned priority at call intake. Maps to incident.priority_level. Represents the INITIAL priority only — do not overwrite with on-scene EMT triage acuity.

Number of patients associated with this incident/dispatch. Maps to incident.number_of_patients. Kept at the EpisodeOfCare (incident) level, not duplicated on child Encounters. If >1, expect multiple EMEpisodeOfCare/Patient chains linked via identifier:groupIncidentId.

Permitted AVPU responsiveness values.

Drug/allergen active-component codes used for allergen and medication coding.

ValueSet identifying who reported an allergy.

ValueSet for ambulance case rejection reasons.

ValueSet for ambulance case status.

ValueSet for types of clinical assessments.

ValueSet for breathing state classification.

ValueSet for prioritizing cases.

ValueSet identifying the source coding system.

ValueSet for condition severity statuses.

ValueSet for units used in medication dosing.

Value set for the incidentPriority extension. Maps to incident.priority_level.

Permitted ABCDE assessment letters.

Permitted age-group buckets used to select a reference range.

Permitted body regions examined during an emergency secondary survey.

Permitted breathing-status values.

Permitted relationships between an emergency caller and the patient.

Permitted emergency-care capability classifications for destination facilities.

Permitted modes of arrival at the emergency department.

Permitted ED encounter dispositions.

Permitted injury intents for a trauma presentation.

Permitted mechanisms of injury for a trauma presentation.

Permitted mobility statuses recorded at ED registration.

Fixed section list for EMEDPatientRecordComposition.

Permitted payment methods recorded at ED registration.

Permitted presentation types (acute/chronic).

Permitted substance-use types.

Permitted facility types for an emergency transport destination.

Permitted diagnostic stages for an emergency Condition instance.

Permitted dispatch priorities assigned during emergency call intake.

Permitted WHO Emergency Unit high-risk sign codes.

Permitted high-level classifications of emergency incidents.

Permitted cardiac-activity findings on a cardiac POCUS view.

Permitted structured POCUS findings.

Permitted RV-function findings on a cardiac POCUS view.

Permitted point-of-care ultrasound views.

Allowed official identifier types for an emergency patient in Kenya.

Permitted ED Physical Exam body systems/regions.

Permitted roles for personnel assigned to an emergency responder unit.

Permitted ownership categories for an emergency responder unit.

Permitted real-time response states for an emergency responder unit.

Permitted types of vehicles and mobile units participating in an emergency response.

Permitted Review of Systems body systems.

Permitted classifications for emergency incident scene locations.

Permitted secondary-survey region examination codes.

Permitted types of emergency-response organizations participating in an incident.

Permitted semi-quantitative dipstick results.

Permitted qualitative descriptors for a vital-sign reading.

ValueSet for types of clinical entries in the health record.

ValueSet containing investigation codes for procedures.

Permitted Kenya health-system facility levels.

Clinical manifestations and symptoms.

ValueSet for routes of medication administration.

Local procedure code list, supplementing SNOMED CT procedure codes.

ValueSet for pulse state classification.

ValueSet for classifying types of questionnaires.

List of Vital Signs LOINC codes

AVPU scale used to describe a patient's responsiveness.

Active pharmaceutical ingredient codes from MOH PPB OCL.

Supplementary instructions for dispensed or administered medication. Source: MOH-KENYA OCL ADDITIONAL-INSTRUCTION-CODES.

Codes for the use of an address. Codes align with FHIR address-use to allow required binding as a subset.

Codes for adjudication result categories. Codes align with FHIR adjudication.

Locally defined financial adjustment types

Codes for the method of medication administration, replacing SNOMED CT-based HL7 ValueSet

Codes for administrative gender. Codes align with FHIR administrative-gender to allow required binding as a subset.

Identifies the source reporting an allergy.

Defines reasons for rejecting an ambulance case.

Defines the lifecycle statuses of an ambulance case.

Units of measurement for annual service quantities

Body site codes for site of medication administration. Source: MOH-KENYA OCL APPROACH-SITE-CODES.

Codes for the condition that triggers as-needed medication use, replacing SNOMED CT-based HL7 ValueSet

Specifies types of clinical assessments for patient evaluation.

Codes classifying the type of attachment submitted with a claim (e.g. Discharge Summary, Final Bill).

Locally defined reasons for failed authorization attempts

Locally defined status values for authorization workflows

Types of authentication or authorization used for healthcare access

A code system that defines categories for Institutional Body Sites

Clinical classification of breathing rate states.

Statuses used to track bulk remittance processing

Category codes for care plan types. Source: MOH-KENYA OCL CARE-PLAN-CATEGORY.

Defines priority levels for cases.

Codes for civil/marital status (MOH-Kenya OCL: CIVIL-STATUS)

Codes for the role of a care team member in a claim (MOH-Kenya OCL: CLAIM-CARE-TEAM-ROLE)

Codes for claim or preauthorization expiry types in Kenya eClaims.

Codes for claim supporting information categories. Codes align with FHIR claiminformationcategory.

Codes for the specific workflow state of a claim in Kenya eClaims.

Codes for the status of a claim. Codes align with FHIR fm-status to allow required binding as a subset.

Kenya-specific codes for the subtype of claim (MOH-Kenya OCL: CLAIM-SUBTYPE).

Codes for the type of claim. Codes align with FHIR claim-type to allow required binding as a subset.

Codes for the intended use of a claim. Codes align with FHIR claim-use to allow required binding as a subset.

Locally defined healthcare service departments for claims

CodeSystem for Code systems

CodeSystem for Contact Relationship

CodeSystem for patient's identifier Types

CodeSystem for patient's title

Identifies the terminology source from which a clinical code originates.

A code system that defines categories for Social Health Authority Interventions

Category codes for Condition resources. Based on FHIR standard condition-category codes (OCL collection was empty).

Clinical status codes for Condition resources. Source: MOH-KENYA OCL CONDITION-CLINICAL-STATUS (supplemented with standard FHIR codes).

Local codes for conditions/diagnoses (MOH-Kenya: CONDITION-CODES)

Codes for the clinical severity of a condition, replacing SNOMED CT-based HL7 ValueSet

Staging codes for oncology and other staged conditions. Source: MOH-KENYA OCL CONDITION-STAGE.

Clinical severity statuses for a patient condition.

Codes for the verification status of a condition. Codes align with FHIR condition-ver-status to allow required binding as a subset.

Codes for contact point systems. Codes align with FHIR contact-point-system to allow required binding as a subset.

Codes for contact point use. Codes align with FHIR contact-point-use to allow required binding as a subset.

Locally defined types of copay sources

Codes for insurance coverage class categories (MOH-Kenya OCL: COVERAGE-CLASS)

Codes for the status of a coverage member (MOH-Kenya OCL: COVERAGE-MEMBER-STATUS)

Codes for types of coverage plan (MOH-Kenya OCL: COVERAGE-PLAN-TYPE)

Codes for the type of insurance coverage (MOH-Kenya OCL: COVERAGE-TYPE)

Levels or types of ICD diagnosis classifications

Codes for diagnosis type. Codes align with FHIR ex-diagnosistype.

Codes for additional dispensing/dosage instructions, replacing SNOMED CT-based HL7 ValueSet

Units used to specify medication doses.

Dispatcher-assigned priority levels at call intake.

Which letter of the ABCDE resuscitation assessment an Observation instance represents.

Identifies the specific structured field carried by a component on EMABCDEAssessmentObservation. Which fields are applicable depends on the parent Observation.code (airway/breathing/circulation/disability/exposure).

Age-group bucket used to select the applicable clinical reference range for an emergency observation.

Body regions examined during an emergency secondary survey.

Caller- or practitioner-reported categories describing the patient's apparent breathing status.

Relationship of an emergency caller to the patient.

Emergency-care capabilities available at a receiving health facility.

Clinical acuity assigned by an emergency practitioner after patient assessment. This terminology is distinct from dispatch priority.

How the patient arrived at the emergency department.

Outcome of the emergency department encounter.

Intent behind a trauma presentation.

Mechanism of injury for a trauma presentation.

Patient's mobility status recorded at ED registration.

Fixed section list for EMEDPatientRecordComposition, mirroring the paper ED Patient Record form.

Payment method recorded at ED registration.

Whether the presenting problem is acute or chronic.

Type of substance used in the last 6 hours, if reported.

Types of healthcare locations that may receive an emergency patient.

Diagnostic stage represented by an emergency Condition instance, from initial chief complaint through discharge diagnosis.

Priority assigned to an emergency incident during call intake.

Codes identifying emergency encounter settings that are not adequately represented by the standard ActCode code system.

Roles performed by people or organizations involved in an emergency incident.

Identifies which WHO Emergency Unit high-risk sign a component on EMHighRiskSignsObservation represents.

High-level classification of an emergency incident.

Categories used to distinguish emergency observations by their source and clinical verification status.

Local codes for emergency medical observations not adequately represented by a single preferred external terminology code.

Whether cardiac activity was visualized on a cardiac POCUS view.

Identifies the specific structured field carried by a component on EMPOCUSObservation.

Structured POCUS findings, shared across the abdomen and chest views. Which codes are clinically applicable depends on which component (abdomenFinding or chestFinding) carries the value.

Qualitative right ventricular function on a cardiac POCUS view.

Which point-of-care ultrasound view an EMPOCUSObservation instance represents.

Identifier types used to identify patients receiving emergency or pre-hospital services in Kenya.

Body system/region covered by a single ED Physical Exam Observation instance.

Types of direct patient-care interactions performed during emergency response.

Operational roles performed by personnel assigned to an emergency responder unit.

Ownership category of an organization operating an emergency responder unit.

Current operational response state of an emergency responder unit during an incident.

Types of vehicles and mobile units used during emergency response.

Body system covered by a single Review of Systems Observation instance.

Types of physical locations at which emergency incidents may occur.

Identifies a secondary-survey physical examination as pertaining to a specific body region.

Types of organizations that may participate in an emergency response.

Identifies which dipstick analyte a component on EMUrinalysisObservation represents.

Semi-quantitative dipstick result scale.

Qualitative descriptor of a vital-sign reading that is independent of, and supplements, its numeric value.

Codes for the status of an encounter. Codes align with FHIR encounter-status to allow required binding as a subset.

Defines the type of clinical entry recorded in the health record.

Codes for the status of an episode of care. Codes align with FHIR episode-of-care-status to allow required binding as a subset.

Codes for the type of episode of care (MOH-Kenya OCL: EPISODE-OF-CARE-TYPE)

A code system that defines Exclusion

Local flag types for marking entities with special statuses

Pharmaceutical formulation/dosage form codes from MOH PPB OCL.

Locally defined codes representing patient funding mechanisms

Extended gender identity codes for Kenya (MOH-Kenya OCL: GENDER). Extends beyond FHIR administrative-gender with additional local codes.

Generic medicinal product codes from MOH PPB OCL.

Codes for types of identifiers used in Kenya (MOH-Kenya OCL: IDENTIFIER-TYPES)

Codes for the use of an identifier. Codes align with FHIR identifier-use to allow required binding as a subset.

Defines Investigation Codes for Procedures.

CodeSystem for KHTS.A Counties in Kenya

Locally defined health service types used for scheduling, classification, or registration.

CodeSystem representing data elements used in KPS.A Client Registration.

CodeSystem representing clinical consultation data elements under the Kenya Patient Summary (KPS.B).

CodeSystem representing clinical status

CodeSystem representing diagnostic data elements under the Kenya Patient Summary (KPS.C).

CodeSystem representing treatment and medication-related data elements under the Kenya Patient Summary (KPS.D).

CodeSystem representing immunization-related data elements under the Kenya Patient Summary (KPS.E).

CodeSystem representing referral-related data elements under the Kenya Patient Summary (KPS.G).

Levels used to classify health facilities in the Kenya health system.

Clinical manifestations and symptoms used in allergy reactions, conditions, and observations. Source: MOH-KENYA OCL MANIFESTATION-OR-SYMPTOM.

Specifies the route by which a medication is administered.

Route of administration codes used in MedicationAdministration. Source: MOH-KENYA OCL MEDICATION-ADMINISTRATION-ROUTE.

Codes representing priority levels for MedicationRequest.

Codes for the reason a medication was stopped or paused, replacing SNOMED CT-based HL7 ValueSet

Reasons for a MedicationAdministration status (e.g. patient refused, not available). Source: MOH-KENYA OCL MEDICATION-ADMIN-STATUS-REASON.

Reasons for a MedicationDispense status (e.g. out-of-stock, patient refused). Source: MOH-KENYA OCL MEDICATIONDISPENSE-STATUS-REASON.

Status codes used for MedicationRequest resources.

Reasons for a MedicationRequest status change (e.g. cancelled, on-hold). Source: MOH-KENYA OCL MEDICATIONREQUEST-STATUS-REASON.

Codes for the use of a name. Codes align with FHIR name-use to allow required binding as a subset.

Status codes for non-EDI claim workflows

Methods used to perform clinical observations. Source: MOH-KENYA OCL OBSERVATION-METHODS.

Codes for the party to be reimbursed. Codes align with FHIR payeetype.

Locally defined payment mechanisms for healthcare services

Codes for payment methods (MOH-Kenya OCL: PAYMENT-METHOD)

A code system that defines PreAuth Exclusions

Clinical procedure codes used in care plan activities and service requests. Source: MOH-KENYA OCL PROCEDURE-CODE.

Codes for financial processing priority. Codes align with FHIR processpriority to avoid dependencies on draft core artifacts.

Clinical classification of pulse rate states.

Categories used to classify questionnaires or assessments.

Reasons for a MedicationStatement status (e.g. stopped, completed). Source: MOH-KENYA OCL REASON-MEDICATION-STATUS-CODES.

Codes for the relationship between related claims (MOH-Kenya OCL: RELATED-CLAIM-RELATIONSHIP)

Locally defined remittance payment channels

Locally defined remittance processing statuses

Route of administration codes from MOH PPB OCL.

Locally defined codes for scheme classifications

Locally defined codes for health service access points

A code system that defines Subsite

A code system that defines Subsite

Unit of measure codes from MOH PPB OCL.

Locally defined frequencies for service or product usage

LOINC codes commonly used for vital signs observations.

A code system that defines Waiver Type

Identifier system for records created within the Kenya emergency and ambulance services workflow.

Unique national identifier assigned to Kenyan citizens and residents.

Example confirmed severe allergy resulting in anaphylaxis.

Invalid allergy example demonstrating a missing required criticality.

Example explicit no-known-allergy assertion recorded after a full allergy history was taken.

Example composed ED chart tying together the resources above.

Example chief-complaint Condition captured from caller-reported information at T0.

Example confirmed discharge-diagnosis Condition recorded at facility handover.

Example chief complaint recorded at ED registration.

Example confirmed discharge diagnosis recorded at ED disposition.

Invalid discharge-diagnosis example demonstrating verificationStatus left as 'provisional' instead of 'confirmed', violating invariant em-condition-1.

Example pre-existing comorbidity captured from the ED intake checklist.

Example working-diagnosis Condition recorded after on-scene assessment.

Example ECG investigation result flagging an anterior STEMI.

Example CBC investigation result ordered during the ED assessment.

Invalid diagnostic report example demonstrating a missing required category, tightened to 1..1 on this profile though optional in base DiagnosticReport.

Example ED encounter following handover from the pre-hospital point-of-care Encounter.

Example root emergency incident Encounter for a road traffic trauma case.

Example point-of-care Encounter for direct patient assessment and treatment during the incident above.

Example must-see alert referencing the high-criticality Domiphen allergy above.

An intentionally non-conformant Patient instance used to demonstrate validation errors against the Emergency Patient profile.

Example receiving facility for emergency transport.

Example emergency incident scene location.

Example real-time position of the ambulance responding to the incident.

Example analgesia given after chest tube insertion.

Example emergency medication administration during resuscitation.

Invalid medication administration example demonstrating a missing encounter context, tightened to 1..1 on this profile though optional in base MedicationAdministration.

Example breathing assessment showing reduced right-sided breath sounds, consistent with the suspected pneumothorax.

Example circulation assessment during initial resuscitation.

Example blood-pressure panel with systolic and diastolic components.

Example heart rate recorded at ED arrival.

Example heart rate recorded at final reassessment prior to disposition.

Example GCS total with eye/verbal/motor sub-scores captured separately.

Example heart-rate vital sign showing a critical qualitative pulse state.

Example high-risk-signs checklist showing poor perfusion present.

Example POCUS chest view confirming a right pneumothorax.

Example general exam with no findings, explicitly recorded.

Example respiratory exam finding correlating with the suspected pneumothorax.

Example GI review of systems with no findings, explicitly recorded.

Example respiratory review of systems with a positive finding.

Invalid exam example: a finding is coded but noFindingsOnExam is left true, violating invariant em-exam-1.

Example head examination with no abnormal findings, explicitly recorded.

Example upper-extremities examination with a coded abnormal finding.

Example standalone triage acuity reassessment, distinct from EMPOCEncounter.priority.

Example urinalysis dipstick panel.

Invalid vital signs example demonstrating a missing required value.

Example facility operating the emergency department.

Example emergency medical services provider and dispatch organization.

An identified adult patient receiving emergency care, referenced across the supporting example chain.

Example paramedic involved in ambulance response and emergency handover.

Example nurse responsible for the patient during the ED encounter.

Example chest tube insertion for the confirmed right pneumothorax.

Example emergency airway procedure performed during transport.

Invalid procedure example demonstrating a missing required code, the specific procedure performed.

A valid unidentified emergency patient with a temporary tracking number, approximate age, and triage-level adult status.