# ePCR National Dataset and Regulatory Exports

## Overview

Ambulance services are often asked to report the same episode of care in different national or regional formats depending on who receives the data. One regulator wants a pseudonymised national return, another wants a structured quality dataset, and a cross-border partner wants the same encounter represented in a different national schema. Rebuilding that mapping manually for every programme creates reporting delay and governance risk.

The National Dataset Exports module gives the platform a controlled way to turn the operational ePCR record into jurisdiction-specific reporting outputs without asking crews to document the same case twice. A service can run local operations in one clinical workspace, then publish the correct dataset for Irish, UK, US, research, or shared-care reporting from the same underlying encounter history.

```mermaid
flowchart TD
    A[Completed ePCR Encounter] --> B[Export Policy and Jurisdiction Check]
    B --> C[National Dataset Mapping]
    C --> D[Irish Reporting Profile]
    C --> E[NEMSIS-Compatible Profile]
    C --> F[JRCALC-Oriented Profile]
    C --> G[Research or Shared-Care Profile]
    D --> H[Governance Review]
    E --> H
    F --> H
    G --> H
    H --> I[Submission or Controlled Sharing]
```

**Last Reviewed:** 2026-04-22
**Last Updated:** 2026-04-22

## Key Features

- **Multi-Profile National Returns**: Generate the same encounter in different reporting profiles so a service can support more than one national or contractual reporting obligation from one documentation workflow.

- **Irish Pre-Hospital Reporting**: Support the Irish national return pattern for ambulance activity and quality reporting without requiring a separate data collection process outside the ePCR workflow.

- **NEMSIS-Compatible Export**: Produce a US-style EMS reporting output for agencies, state programmes, or partners that expect NEMSIS-aligned structure.

- **JRCALC-Oriented Export**: Support UK-style structured returns for services, pilots, or partner programmes working to JRCALC-aligned reporting expectations.

- **Tenant-Level Export Policy**: Let each organisation decide which national profile is active for its environment so one shared platform can serve multiple jurisdictions cleanly.

- **Pseudonymised Reporting for Secondary Use**: Support national reporting and analytics use cases without exposing more patient-identifying information than the receiving workflow requires.

- **Human Review Before Submission**: Give reporting teams a reviewable output that can be checked by governance or quality teams before external submission.

- **Export Audit History**: Preserve when a dataset was generated, which reporting profile was used, and what period it covered so services can evidence submission activity later.

## Use Cases

- **Irish Ambulance Service Return**: A service produces its scheduled national activity submission from the live ePCR record instead of maintaining a second spreadsheet-based reporting process.

- **Cross-Border Operating Model**: An operator serving more than one jurisdiction keeps one field workflow but issues different reporting outputs depending on the receiving regulator or partner programme.

- **Clinical Quality Programme**: A governance team extracts a structured encounter set for stroke, STEMI, or non-conveyance review without asking crews to re-enter case data in a quality portal.

- **Research and Improvement Work**: A service prepares a controlled export for audit, service redesign, or approved research using the same documented encounter record that supported operational care.

- **Commissioned Service Reporting**: A contracted specialist unit provides the funder with the format they expect while still documenting care in the platform's standard clinical workspace.

## Integration

- **Electronic Patient Care Report Clinical Workspace**: The export profiles use the encounter, handover, intervention, and audit data already captured during care delivery.

- **Clinical Governance and Audit**: Review teams can validate completeness and quality before a dataset leaves the platform.

- **National Services and Health-System Connectors**: Where a receiving authority or health programme supports digital submission, the export module becomes the bridge between the operational ePCR and the national reporting channel.

- **Analytics and Data Warehouse Workflows**: The same structured outputs can support internal performance analysis and approved downstream data-sharing programmes.

## Open Standards

- **NEMSIS v3.5**: supports export into the widely adopted EMS reporting structure used by US-aligned emergency medical services programmes.

- **HL7 FHIR R4 Bulk Data Access**: supports larger-scale secondary-use and data-lake style exchange where a receiving programme consumes standards-based healthcare data export.

- **SNOMED CT**: clinical concepts can remain interoperable when exported into structured downstream reporting and analytics workflows.

- **ICD-10 and ICD-10-AM**: diagnosis and outcome coding can be aligned to common reporting and quality-review vocabularies.

- **CSV and JSON**: the module supports common open data interchange formats for regulated reporting, quality review, and controlled analytics workflows.