Abstract, sectioned logical model for the PH Road Safety MDS covering incident, patient, encounter, clinical, vitals, injuries, evidence/documents, workflow, and finance. Elements mirror the CSV rows; mappings point to target FHIR elements for subsequent profiling.

Composition for facility/ONEISS navigation, structured into coded sections derived from the Road Safety MDS (ED vitals, conditions, outcome, documents, tasks). Enables IG UIs to present a consistent outline.

Composition for EMS Run Report navigation, structured into coded sections derived from the Road Safety MDS (triage, vitals, counts, post‑crash, documents, tasks). Enables IG UIs to present a consistent outline.

ONEISS: ICD-10 external cause codes (V01–Y36 etc.).

ONEISS: ICD-10 nature of injury codes (S00–T98).

ONEISS: Initial impression on patient condition.

MDS89: Problem (chief complaint as code/text).

MDS115: Post-crash report reference (URL preferred).

DocumentReference profile for the ONEISS facility report (scan or link).

Run Report scanned form or structured document (MDS5/MDS4 workflow docs).

MDS221: Party-at-fault narrative/report.

MDS225: Geospatial resources references.

MDS224: Incident management logs/evidence.

MDS226: Vehicle condition documents; alternative structured observations may exist.

Encounter profile for facility visits (ONEISS). Contains hospital identifiers and hospitalization.dischargeDisposition.

Encounter for EMS transport/run-report. Incorporates MDS: Incident number (req), Type/class, Received-by participant role.

Bundle profile that prescribes the required slices/resources for facility (ONEISS) submissions.

Represents a hospital available for EMS referral, linked to its location.

It is intended to support documentation of external causes, nature and extent of injuries, vital signs, Glasgow Coma Scale, and other clinical or scene observations related to road traffic incidents.

Location profile for crash/incident scene with optional geocoordinates and free-text reference to road network shapefiles or external resources.

MDS76-77: Vital sign at scene (BP panel with systolic/diastolic).

MDS227: CCTV video/reconstruction available.

MDS218: Collision type (Must Support).

MDS108: Alive/Dead or other condition upon assessment.

MDS81: Cyanosis presence/type.

MDS62: Date received; single anchor dateTime.

ONEISS: Vital sign at facility (BP panel).

ONEISS: Vital sign at facility (HR).

MDS109: Extent/severity estimate/category (free text/category).

Generic pattern for boolean flag with optional coded specifics for external causes (bites, burns, drowning, etc.).

Observation profile for facility-collected vitals and clinical observations for ONEISS reporting. Intended to be derived from PH‑CORE Observation profile when available.

MDS83-86: GCS modeled as components (eyes, verbal, motor) with optional total integer.

MDS73: Vital sign at scene (HR).

MDS79: LOC; bind to AVPU/GCS category where available.

MDS118/119: Mode of transport to hospital/facility with optional free-text.

ONEISS: Outcome/condition at discharge (MDS53/58).

MDS157: How many patients involved (integer).

MDS80: Pupils size/reactivity summary.

MDS70: Respiratory rate with MS, optional rhythm/breath sounds captured elsewhere.

Base for scene/transport observations in the Run Report derived from MDS. Provides common elements and Must Support flags where applicable.

MDS116/117: Status upon reaching facility (e.g., conscious/unconscious).

MDS78: Temperature with MS; method/site optional in notes or components.

MDS66: Depart scene timestamp.

MDS64: Unit dispatched/enroute timestamp.

MDS67: Arrival at hospital timestamp.

MDS65: Arrival on scene timestamp.

MDS63: Use single dateTime; stored as valueDateTime.

MDS68: Station return/available timestamp.

MDS41: Required flag for RS reporting.

MDS111: Priority to Scene (Triage).

MDS156: How many vehicles involved (integer).

Profile for recording refusal to admit a patient.

Profile for recording allergy or intolerance information in the Philippine Road Safety IG.

A Claim profile for PH Road Safety IG requiring total.

Condition profile for coding diagnoses, ICD-10 nature of injury, and external cause mappings required by the Road Safety MDS.

A Condition for the Safety of the Roads in the Philippines.

A profile to capture documents related to road safety incidents in the Philippine context.

Encounter profile for road safety reporting (hospital case no, incident no, transport details, disposition, etc.)

A profile representing a patient's current medication statement for the Philippine health context.

A profile for Road Safety resource specific to Philippine context.

Procedure profile for road safety and injury surveillance.

• Captures interventions performed on the patient.
• Supplies used during the procedure.
• Coordination with receiving hospital if applicable.

A profile on Questionnaire to capture repeating Vital Signs data (Respiratory Rate, Pulse, Blood Pressure, Temperature, LOC).

A profile for tasks related to road safety, tracking report forms and delays.

Task profile for workflow events related to report submission, coordination with receiving facilities, and delays (executionPeriod, notes) in the Road Safety MDS.

Bundle profile that prescribes required slices/resources for EMS run reports.

MDS9-10: Sources of delays, Duration of delay.

Patient age, derived from birthDate. Not intended for direct data entry.

Cause or contributing factor of the road crash.

Indicates if the emergency department is currently accepting patients.

Additional detail for external cause (e.g., specify animal/insect, weapon, burn type).

Indicates whether first aid was provided to the patient.

Temporary local copy of PH Core Occupation extension for Road Safety testing

Identifies the party considered at fault in the road crash.

Whether the report form was received as digital or physical.

Metadata reference to detailed road network shapefile related to the incident.

Records any devices or medications used during the procedure.

Documentation or status of traffic incident management.

Indicates if transport to receiving hospital was coordinated.

Details about mode of transport, vehicles involved, positions.

Condition of the vehicle involved in the incident.

The type of vehicle used by the patient or involved in the encounter.

Example ValueSet for Activity at time of incident

Allowed units for Patient Age when Date of Birth is not available.

Combines medical interventions, first aid, and psychosocial procedures.

Allowed file types for documents describing the cause of a road crash.

Defines codes representing the external causes of road traffic crashes

Types of collision in road traffic incidents

Illustrative set of codes representing external causes of injury.

Allowed values for first aid performed.

Categories for hospitals relevant to EMS referral.

AVPU scale coded in SNOMED CT.

Breath sounds by auscultation.

Overall condition assertion (Alive/Dead).

Cyanosis presence/type.

Type/body of water involved in drowning.

GCS Eye opening (LOINC answers).

GCS Motor response (LOINC answers).

GCS Verbal response (LOINC answers).

Intent of injury.

Common injury morphology/types.

Transport mode answer list (LOINC answers).

Outcome at discharge/release.

Pulse quality (normal/thready/bounding).

Pulse rhythm (regular/irregular).

Pupil findings.

Respiratory rhythm findings.

Status upon reaching facility.

Aggregated ValueSet of coded options from the MDS Road Safety dataset, prioritizing SNOMED CT first, then LOINC. One code per sheet row is retained based on this priority.

Procedure codes representing medical interventions.

Sample ValueSet capturing transport modes.

Demonstration ValueSet capturing the nature of injury.

Example ValueSet capturing possible outcomes.

ValueSet indicating the party at fault in an incident.

Example ValueSet capturing places of occurrence.

Codes representing psychosocial support interventions.

ValueSet indicating whether a report form has been received.

Permitted file types for detailed road network shapefiles or GIS documents.

ValueSet for Task.status using custom Road Safety codes.

Standard codes for documenting transport coordination.

Example ValueSet capturing triage priorities.

Vehicle types allowed for Road Safety Encounter

ValueSet indicating the condition of a vehicle.

Allowed file types for detailed road network shapefiles or GIS data.

Custom codes for Task.status specific to Road Safety reporting.

A code system for different types of vehicles used in road safety encounters.

Unique identifier assigned to each hospital case.

The permanent and unique number issued by hospitals to individual patients and their dependents.

Unique identifier assigned to each incident.

The permanent and unique number issued by PhilHealth to individual members and to each and every dependent.

Maps elements from the MDSRoadSafety logical model to target FHIR R4 resources.

Road traffic accident scene for the encounter.

Receiving medical facility for the road safety encounter.

ED Location involved in the encounter.

Hospital submitting the road safety patient report.

Road crash patient referenced by the ServiceRequest example.

Team Leader in the Road Safety Encounter (Dr. Ana Cruz leads the medical response team).

Assistant in the Road Safety Encounter (Nurse John Lee assists the treatment and transport officers).

Transport Officer in the Road Safety Encounter (Dr. Lisa Tan is responsible for patient transfer and transport decisions).

Received By in the Road Safety Encounter (Clerk Maria Santos logs the patient’s arrival at the receiving facility).

Treatment Officer in the Road Safety Encounter (Dr. Mark Reyes provides primary patient treatment).

This example records a refusal to admit a road crash patient during a Road Safety Encounter, including the hospital that refused admission and the physician involved.

Example of a road safety hospital encounter with identifiers, participants, and disposition.

Example of a patient where only age is known.

Example of an elderly patient with approximate age.

Example of a pediatric patient with age in months.

A patient with both permanent and temporary addresses.

Example of a road safety task to track report form receipt and delays.

Hospital referenced in the ServiceRequest example (refused admission).

Example Questionnaire instance to capture repeating sets of Vital Signs.

Example response to the Vital Signs Questionnaire with sample measurements.

Example patient involved in a road traffic crash, aligned to the RoadSafetyProfile.