Use-Case 8: Traffic data

The Traffic administrations collect this data from different sources but does not have information when the injured are foreigners and are transferred to their country. In addition, health competences in some countries are assumed by the autonomous communities or regions and information is not always obtained for all the injured.

Also, effective practice recognizes that no accident database will provide sufficient information to provide a complete view of traffic accident victims to fully understand the causes of injuries. Accident data are a valuable source of information on accident risk, the value of which can be significantly increased when combined with other data sources such as health sector data.

Linking traffic incident reports to individual health profiles using anonymized identifiers and semantic data standards will allow identifying how chronic conditions or medication use contribute to accidents and fatalities.

Data fusion techniques would be applied for correlation analysis, using data mining, machine learning, and semantic interoperability frameworks. Special attention is given to the legal and ethical implications of data access and sharing.

Document Version: V1.0

Responsible Party: xShare WP4

Source:

As-Is Situation 

The national traffic accident victims’ registers collect information from several sources related to accidents, vehicles, police officer, passengers, drivers, pedestrians, etc.  Usually, the information is collected through web services to access to databases as drivers, towns and municipalities and roads catalogues.  In addition, the traffic administrations collect this data from different sources but does not have information when the injured are foreigners and are transferred to their country. Nowadays, there is no correlation between health and road traffic data.

Currently available products/services and its vendors

The public road traffic authorities collect Traffic Data to create the National Traffic Accident Registries, which include detailed information about accidents, such as location, time, road conditions, and characteristics of vehicles and drivers. But usually, there is no correlation with Health Data: medical records, hospitalization histories, diagnoses, and treatments of accident victims. These data can be obtained from EHRs and PHRs.

Which health-related standard does your organisation uses and its alignment to the EEHRxF?

Web services must collect data EHRF-compliant from EHDS.

Actors/Users and their Roles
Healthcare ProvidersCollect data in EEHRxF Format to to be able to exchange data properly
Public road Traffic authoritiesAsk and receive heath data (in origin EEHRxF ) to integrate them in national traffic accident victims’ registries
User Perspective 

The public road traffic authority needs to be able to ask and receive EEHRxF compliant data.

System Perspective 

The national traffic accidents system will be enabled to combine data from EHDS in EEHRxF and traffic data.

Health Information Domain(s) – HIDs: 
  • Electronic prescription
  • Patient Summary
National/regional strategy

National public health and road traffic authorities can share / combine EEHRxF- compliant data so it can be exchanged between different systems and regions.

Strategy towards EHDS

Obtain EEHRxF-compliant data collected right from the source EHDS to have data readily available to support the correlation of traffic accident data with health data. Secondary use of the health data.

Business Goals/Benefits and KPIs

Combining traffic accident data with health records to understand additional accident causes, such as chronic diseases or medication effects (e.g., psychotropics).

Obtain information from EHDS when the injured are foreigners and are transferred to their country.

KPIs
  • Number of cases (accidents) detected caused by chronic diseases or medication effects.
Application

Integrate / combine functionalities for EHR / Electronic Prescriptions and Road traffic registries using the EEHRxF

Data Preconditions

EEHRxF compliance and adherence to specific semantic constraints in order to integrate the health with the road traffic data.

System Preconditions

National system can identify relevant data and trigger a Patient Summary or Electronic Prescription to find out the necessary health data related to the involved people in an accident.

The system has to adapt the information coming from EHDS to its registers. 

Security and Privacy Policies should already be in place.

User Preconditions

Capability of asking/receiving data in EEHRxF format.

Trigger

Need information about a driver or passenger involved in current accident.

Challenges/Limitations

Development needed by all actors in order to properly integrate health and traffic data.

The correlation of traffic accident data with health data might be done by cross-referencing information from the databases. This includes hospital data, public health records, and traffic statistics. By analysing this data together, additional patterns and risk factors can be identified, such as medical conditions that could have contributed to the accidents. This comprehensive approach allows for a better understanding of the underlying causes and the implementation of more effective preventive measures

Involved stakeholders in the BUC definition

UVEG

Application of pseudonymisation filters

Yes- secondary use.

Basic Workflow
  • The national police are usually the first to arrive at the scene of the accident and collect detailed information about the incident, including the location, time, those involved, and the severity of the injuries.
  • The initial information is included in the national traffic accident victims
  • This data is supplemented with information from hospitals to get a more complete picture of serious injuries (EHDS).
  • The anonymized data is stored in national databases and analyzed to identify patterns and causes of accidents, which helps to develop prevention strategies.