DRAFT PH Road Safety Implementation Guide
0.1.0 - ci-build Philippines flag

DRAFT PH Road Safety Implementation Guide, published by UP Manila - National Institutes of Health - National Telehealth Center. This guide is not an authorized publication; it is the continuous build for version 0.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/UPM-NTHC/PH-RoadSafetyIG/ and changes regularly. See the Directory of published versions

Artifacts Summary

This page provides a list of the FHIR artifacts defined as part of this implementation guide.

Structures: Logical Models

These define data models that represent the domain covered by this implementation guide in more business-friendly terms than the underlying FHIR resources.

Road Safety Minimum Dataset (MDS) Logical Model

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.

Structures: Resource Profiles

These define constraints on FHIR resources for systems conforming to this implementation guide.

Composition - Facility Report

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 - Run Report

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.

Condition - ICD-10 External Cause

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

Condition - ICD-10 Nature of Injury

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

Condition - Initial Impression

ONEISS: Initial impression on patient condition.

Condition - Problem / Chief Complaint

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

DocumentReference - Cause of Road Crash

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

DocumentReference - ONEISS Facility Report

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

DocumentReference - ONEISS Run Form

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

DocumentReference - Party at Fault

MDS221: Party-at-fault narrative/report.

DocumentReference - Road Network Shape Files

MDS225: Geospatial resources references.

DocumentReference - Traffic Incident Management

MDS224: Incident management logs/evidence.

DocumentReference - Vehicle Condition

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

Encounter - Facility

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

Encounter - Transport / Run Report

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

Facility Bundle (prescribed)

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

Hospital Available

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

Injury Observation

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 - Incident / Scene

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

Observation - Blood Pressure

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

Observation - CCTV Available

MDS227: CCTV video/reconstruction available.

Observation - Collision Type

MDS218: Collision type (Must Support).

Observation - Condition of Patient

MDS108: Alive/Dead or other condition upon assessment.

Observation - Cyanosis

MDS81: Cyanosis presence/type.

Observation - Date Received

MDS62: Date received; single anchor dateTime.

Observation - ED Blood Pressure

ONEISS: Vital sign at facility (BP panel).

Observation - ED Heart Rate

ONEISS: Vital sign at facility (HR).

Observation - Extent of Injury

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

Observation - External Cause (Generic)

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

Observation - Facility / ONEISS

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

Observation - Glasgow Coma Scale

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

Observation - Heart Rate

MDS73: Vital sign at scene (HR).

Observation - Level of Consciousness

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

Observation - Mode of Transport to Facility

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

Observation - Outcome at Discharge

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

Observation - Patients Involved Count

MDS157: How many patients involved (integer).

Observation - Pupils

MDS80: Pupils size/reactivity summary.

Observation - Respiratory Rate

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

Observation - Scene / Base

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

Observation - Status on Arrival

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

Observation - Temperature

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

Observation - Time Departed Scene

MDS66: Depart scene timestamp.

Observation - Time Enroute

MDS64: Unit dispatched/enroute timestamp.

Observation - Time Hospital Arrival

MDS67: Arrival at hospital timestamp.

Observation - Time On Scene

MDS65: Arrival on scene timestamp.

Observation - Time Received

MDS63: Use single dateTime; stored as valueDateTime.

Observation - Time Station Arrival

MDS68: Station return/available timestamp.

Observation - Transport/Vehicular Accident Flag

MDS41: Required flag for RS reporting.

Observation - Triage Category (Scene)

MDS111: Priority to Scene (Triage).

Observation - Vehicles Involved Count

MDS156: How many vehicles involved (integer).

Refusal to Admit Service Request

Profile for recording refusal to admit a patient.

Road Safety AllergyIntolerance

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

Road Safety Claim

A Claim profile for PH Road Safety IG requiring total.

Road Safety Condition

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

Road Safety Condition

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

Road Safety Document Reference

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

Road Safety Encounter

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

Road Safety MedicationStatement

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

Road Safety Patient

A profile for Road Safety resource specific to Philippine context.

Road Safety Procedure

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.
Road Safety Questionnaire

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

Road Safety Task

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

Road Safety Task

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

Run Report Bundle (prescribed)

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

Task - Delay Reporting

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

Structures: Extension Definitions

These define constraints on FHIR data types for systems conforming to this implementation guide.

Age

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

Cause of Road Crash Incident

Cause or contributing factor of the road crash.

Emergency Department Availability

Indicates if the emergency department is currently accepting patients.

External Cause Detail

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

First Aid Given

Indicates whether first aid was provided to the patient.

PH Core Occupation (Stub)

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

Party at Fault

Identifies the party considered at fault in the road crash.

Report Form Received

Whether the report form was received as digital or physical.

Road Network Shape File

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

Safety / Other Risk Factors
Supplies Used

Records any devices or medications used during the procedure.

Traffic Incident Management

Documentation or status of traffic incident management.

Transport Coordination

Indicates if transport to receiving hospital was coordinated.

Transport Details

Details about mode of transport, vehicles involved, positions.

Vehicle Condition

Condition of the vehicle involved in the incident.

Vehicle Used

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

Vehicle list

Terminology: Value Sets

These define sets of codes used by systems conforming to this implementation guide.

Activity ValueSet (example)

Example ValueSet for Activity at time of incident

Age Units ValueSet

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

All Road Safety Procedure Codes

Combines medical interventions, first aid, and psychosocial procedures.

Cause of Crash File Type ValueSet

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

Cause of Road Crash

Defines codes representing the external causes of road traffic crashes

Collision Type ValueSet (example)

Types of collision in road traffic incidents

Disposition values (sample)
Document formats (sample)
External Cause ValueSet (example)

Illustrative set of codes representing external causes of injury.

First Aid Codes

Allowed values for first aid performed.

Hospital / EMS Category

Categories for hospitals relevant to EMS referral.

ICD-10 External Cause (sample)
ICD-10 Nature of Injury (sample)
MDS AVPU Level of Consciousness

AVPU scale coded in SNOMED CT.

MDS Breath Sounds

Breath sounds by auscultation.

MDS Condition of Patient

Overall condition assertion (Alive/Dead).

MDS Cyanosis

Cyanosis presence/type.

MDS Drowning Body of Water

Type/body of water involved in drowning.

MDS GCS Eyes

GCS Eye opening (LOINC answers).

MDS GCS Motor

GCS Motor response (LOINC answers).

MDS GCS Verbal

GCS Verbal response (LOINC answers).

MDS Injury Intent

Intent of injury.

MDS Injury Types

Common injury morphology/types.

MDS Mode of Transport to Facility

Transport mode answer list (LOINC answers).

MDS Outcome

Outcome at discharge/release.

MDS Pulse Quality

Pulse quality (normal/thready/bounding).

MDS Pulse Rhythm

Pulse rhythm (regular/irregular).

MDS Pupils

Pupil findings.

MDS Respiratory Rhythm

Respiratory rhythm findings.

MDS Status on Arrival

Status upon reaching facility.

MDSRoadSafety ValueSet

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.

Medical Intervention Procedure Codes

Procedure codes representing medical interventions.

Mode of Transport ValueSet (example)

Sample ValueSet capturing transport modes.

Nature of Injury ValueSet (example)

Demonstration ValueSet capturing the nature of injury.

Outcome ValueSet (example)

Example ValueSet capturing possible outcomes.

Party at Fault

ValueSet indicating the party at fault in an incident.

Place of Occurrence ValueSet (example)

Example ValueSet capturing places of occurrence.

Psychosocial Procedure Codes

Codes representing psychosocial support interventions.

Report Form Received

ValueSet indicating whether a report form has been received.

Road Network File Type

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

Road Safety Task Status

ValueSet for Task.status using custom Road Safety codes.

Transport Coordination Codes

Standard codes for documenting transport coordination.

Triage Priority ValueSet (example)

Example ValueSet capturing triage priorities.

Triage categories (sample)
ValueSet for Vehicle Used

Vehicle types allowed for Road Safety Encounter

Vehicle Condition

ValueSet indicating the condition of a vehicle.

Terminology: Code Systems

These define new code systems used by systems conforming to this implementation guide.

Activity at time of incident (example)
Cause of Road Crash
Collision Type (example)
External Cause CodeSystem (example)
Facility Composition Sections
Mode of Transport (example)
Nature of Injury (example)
Outcome (example)
Party at Fault
Place of Occurrence (example)
Report Form Received
Road Network File Type

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

Road Safety Composition Type (Facility)
Road Safety Composition Type (Run)
Road Safety Task Status Codes

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

Run Report Composition Sections
Triage Priority (example)
Vehicle Condition
Vehicle Types

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

Terminology: Naming Systems

These define identifier and/or code system identities used by systems conforming to this implementation guide.

Hospital Case Number System

Unique identifier assigned to each hospital case.

Hospital Patient ID No.

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

Incident Number System

Unique identifier assigned to each incident.

National Health Facility Registry ID

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

Terminology: Concept Maps

These define transformations to convert between codes by systems conforming with this implementation guide.

MDS Logical Model to FHIR Mapping

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

Example: Example Instances

These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like.

Accident Scene Location

Road traffic accident scene for the encounter.

City General Hospital

Receiving medical facility for the road safety encounter.

City General Hospital - Emergency Department

ED Location involved in the encounter.

Example Hospital Organization

Hospital submitting the road safety patient report.

Patient - Jose Dela Cruz

Road crash patient referenced by the ServiceRequest example.

Practitioner - Ana Cruz

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

Practitioner - John Lee

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

Practitioner - Lisa Tan

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

Practitioner - Maria Santos

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

Practitioner - Mark Reyes

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

Refusal to Admit Service Request Example

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.

Road Safety Encounter Example

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

Road Safety Patient Example - Age Only

Example of a patient where only age is known.

Road Safety Patient Example - Elderly

Example of an elderly patient with approximate age.

Road Safety Patient Example - Infant Age

Example of a pediatric patient with age in months.

Road Safety Patient Example - With Two Addresses

A patient with both permanent and temporary addresses.

Road Safety Task Example

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

St. Jaylord's Medical Center

Hospital referenced in the ServiceRequest example (refused admission).

Vital Signs Questionnaire

Example Questionnaire instance to capture repeating sets of Vital Signs.

Vital Signs QuestionnaireResponse Example

Example response to the Vital Signs Questionnaire with sample measurements.

patient-road-safety-ex

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