{"id":"epcr-national-dataset-exports","slug":"epcr-national-dataset-exports","title":"ePCR National Dataset and Regulatory Exports","description":"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 str","category":"modules","tags":["modules","geospatial"],"lastModified":"2026-04-22","source_ref":"content/modules/epcr-national-dataset-exports.md","url":"/developers/epcr-national-dataset-exports","htmlPath":"/developers/epcr-national-dataset-exports","jsonPath":"/api/docs/modules/epcr-national-dataset-exports","markdownPath":"/api/docs/modules/epcr-national-dataset-exports?format=markdown","checksum":"e68e1b85d54c7c536cf79c00e0b7c3c68f5adb20dd08aaf3605f5d0c0a6002e3","headings":[{"id":"overview","text":"Overview","level":2},{"id":"key-features","text":"Key Features","level":2},{"id":"use-cases","text":"Use Cases","level":2},{"id":"integration","text":"Integration","level":2},{"id":"open-standards","text":"Open Standards","level":2}],"markdown":"# ePCR National Dataset and Regulatory Exports\n\n## Overview\n\nAmbulance 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.\n\nThe 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.\n\n```mermaid\nflowchart TD\n    A[Completed ePCR Encounter] --> B[Export Policy and Jurisdiction Check]\n    B --> C[National Dataset Mapping]\n    C --> D[Irish Reporting Profile]\n    C --> E[NEMSIS-Compatible Profile]\n    C --> F[JRCALC-Oriented Profile]\n    C --> G[Research or Shared-Care Profile]\n    D --> H[Governance Review]\n    E --> H\n    F --> H\n    G --> H\n    H --> I[Submission or Controlled Sharing]\n```\n\n**Last Reviewed:** 2026-04-22\n**Last Updated:** 2026-04-22\n\n## Key Features\n\n- **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.\n\n- **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.\n\n- **NEMSIS-Compatible Export**: Produce a US-style EMS reporting output for agencies, state programmes, or partners that expect NEMSIS-aligned structure.\n\n- **JRCALC-Oriented Export**: Support UK-style structured returns for services, pilots, or partner programmes working to JRCALC-aligned reporting expectations.\n\n- **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.\n\n- **Pseudonymised Reporting for Secondary Use**: Support national reporting and analytics use cases without exposing more patient-identifying information than the receiving workflow requires.\n\n- **Human Review Before Submission**: Give reporting teams a reviewable output that can be checked by governance or quality teams before external submission.\n\n- **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.\n\n## Use Cases\n\n- **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.\n\n- **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.\n\n- **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.\n\n- **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.\n\n- **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.\n\n## Integration\n\n- **Electronic Patient Care Report Clinical Workspace**: The export profiles use the encounter, handover, intervention, and audit data already captured during care delivery.\n\n- **Clinical Governance and Audit**: Review teams can validate completeness and quality before a dataset leaves the platform.\n\n- **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.\n\n- **Analytics and Data Warehouse Workflows**: The same structured outputs can support internal performance analysis and approved downstream data-sharing programmes.\n\n## Open Standards\n\n- **NEMSIS v3.5**: supports export into the widely adopted EMS reporting structure used by US-aligned emergency medical services programmes.\n\n- **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.\n\n- **SNOMED CT**: clinical concepts can remain interoperable when exported into structured downstream reporting and analytics workflows.\n\n- **ICD-10 and ICD-10-AM**: diagnosis and outcome coding can be aligned to common reporting and quality-review vocabularies.\n\n- **CSV and JSON**: the module supports common open data interchange formats for regulated reporting, quality review, and controlled analytics workflows.\n"}