Search loading...

API Hub

Explore and Make use of Nationally Defined Messaging APIs

 

Emergency Care Attendance Event Message Bundle

The FHIR profiles used for the Emergency Care Attendance Event Message Bundle

FHIR Profiles

The following FHIR profiles are used to form the Emergency Care Attendance Event Message Bundle:

Bundle Structure

Specifies referencing within the Event Message Bundle.


Emergency Care Attendance (open in new TAB)

Emergency Care Attendance Event data item mapping to FHIR profiles

This Mapping table defines the FHIR elements that SHALL be used to encode the Healthy Child Event Specification data items for each DCH Event Message payload.
Some common data item mappings, such as patient, publisher or Date/Time of event information, are defined within the Header mapping table and SHALL be considered in parallel with the payload mapping.

The Child Health Event data items are fulfilled by elements within the FHIR resources listed below:

DCH Data ItemFHIR resource elementMandatory/
Required/
Optional
Note
Date and Time of attendanceCareConnect-Encounter-1.period.startMandatory
Date and Time of dischargeCareConnect-Encounter-1.period.endRequired
ODS/ORD Site CodeCareConnect-Location-1.identifier (ODS Site Code)Required
Accompanied by (Name)CareConnect-RelatedPerson-1.nameRequired
Accompanied by (Relationship)CareConnect-RelatedPerson-1.relationshipRequired"For Emergency Care Attendance, the relationship code must come from the valueSet provided)"
Attendance SourceCareConnect-Encounter-1.hospitalization.admitSourceRequired
Presenting ComplaintCareConnect-Encounter-1.reasonMandatory
ProcedureCareConnect-Procedure-1.codeRequired
Discharge destinationCareConnect-Encounter-1.hospitalization.dischargeDispositionMandatory
Discharge statusCareConnect-Encounter-1.emergencyDischargeStatusMandatory
Clinical NarrativeCareConnect-Communication-1Optional

Resource Population Requirements and Guidance

The following requirements and resource population guidance should be followed in addition to the requirements and guidance outlined in the data item mapping above and in the Event Header requirements page.

Bundle

Resource Cardinality 1..1
Element Cardinality Additional Guidance
type 1..1 Fixed value: message

Event-MessageHeader-1

The Event-MessageHeader-1 resource included as part of the event message SHALL conform to the Event-MessageHeader-1 constrained FHIR profile and the additional population guidance as per the table below:

Resource Cardinality 1..1
Element Cardinality Additional Guidance
extension(messageEventType) 1..1  
event 1..1 Fixed Value: ‘emergency-care-attendance-1 | Emergency Care Attendance’
responsible 1..1 This will reference the responsible Organization resource
focus 1..1 This will reference the CareConnect-Encounter-1 resource which contains information relating to the event message.

CareConnect-Organization-1

The CareConnect-Organization-1 resource included as part of the event message SHALL conform to the CareConnect-Organization-1 constrained FHIR profile and the additional population guidance as per the table below:

Resource Cardinality 1..*
Element Cardinality Additional Guidance
identifier.system 1..1 Fixed value: https://fhir.nhs.uk/Id/ods-organization-code
identifier.value 1..1 Organisation’s ODS Organization Code
name 1..1 Organisation’s Name

CareConnect-HealthcareService-1

The CareConnect-HealthcareService-1 resource included as part of the event message SHALL conform to the CareConnect-HealthcareService-1 constrained FHIR profile and the additional population guidance as per the table below:

Resource Cardinality 1..1
Element Cardinality Additional Guidance
providedBy 1..1 This will reference the ‘sender’ organization of the event message.
type 1..1 This will represent the type of service responsible for the event message. This will have a fixed value from the ValueSet CareConnect-CareSettingType-1
specialty 1..1 HealthcareService.specialty SHALL use a value from https://fhir.nhs.uk/STU3/ValueSet/DCH-Specialty-1

CareConnect-Patient-1

The CareConnect-Patient-1 resource included as part of the event message SHALL conform to the CareConnect-Patient-1 constrained FHIR profile and the additional population guidance as per the table below:

Resource Cardinality 1..1
Element Cardinality Additional Guidance
identifier 1..1 Patient NHS Number SHALL be included within the nhsNumber identifier slice
name (official) 1..1 Patients name as registered on PDS, included within the resource as the official name element slice
birthDate 1..1 The patient birth date shall be included in the patient resource

CareConnect-Encounter-1

The CareConnect-Encounter-1 resource included as part of the event message SHALL conform to the CareConnect-Encounter-1 constrained FHIR profile and the additional population guidance as per the table below:

Resource Cardinality 1..1
Element Cardinality Additional Guidance
Encounter.type.coding(childHealthEncounterType) 1..1 Encounter.type.coding(childHealthEncounterType) SHALL use a value from https://fhir.nhs.uk/STU3/ValueSet/DCH-ChildHealthEncounterType-1
Encounter.reason.coding(snomedCT) 1..1 Encounter.reason.coding(snomedCT) SHALL use a value from https://fhir.nhs.uk/STU3/ValueSet/DCH-AdmissionReason-1
serviceProvider 1..1 This will reference the Organisation resource hosting the Encounter
location 1..1 This will reference the Encounter’s Location
subject 1..1 This will reference the patient resource representing the subject of this event

CareConnect-Location-1

The CareConnect-Location-1 resource included as part of the event message SHALL conform to the CareConnect-Location-1 constrained FHIR profile and the additional population guidance as per the table below:

Resource Cardinality 0..1

CareConnect-Procedure-1

The CareConnect-Procedure-1 resource included as part of the event message SHALL conform to the CareConnect-Procedure-1 constrained FHIR profile and the additional population guidance as per the table below:

Resource Cardinality TBC
Element Cardinality Additional Guidance
     

CareConnect-RelatedPerson-1

The CareConnect-RelatedPerson-1 resource included as part of the event message SHALL conform to the CareConnect-RelatedPerson-1 constrained FHIR profile and the additional population guidance as per the table below:

Resource Cardinality 0..*
Element Cardinality Additional Guidance
patient 1..1 patient SHALL reference the Patient resource the RelatedPerson is related to
relationship 0..1 RelatedPerson.relationship SHOULD use a value from https://fhir.nhs.uk/STU3/ValueSet/DCH-PersonRelationshipType-1

CareConnect-Communication-1

The CareConnect-Communication-1 resource included as part of the event message SHALL conform to the CareConnect-Communication-1 constrained FHIR profile and the additional population guidance as per the table below:

Resource Cardinality 0..*
Element Cardinality Additional Guidance
Communication.category.coding 1..1 Communication.category.coding SHOULD use a value from https://fhir.nhs.uk/STU3/CodeSystem/DCH-ProfessionalCommentType-1

Emergency Care Attendance Example

Profile Change Mappings for Emergency Care Attendance

Profiles used in Demographics Update Event Messages 1.2.1-Release Candidate are replaced with:

Demographic-Event-Messages Demographic-Event-Messages-CareConnect
DCH-Bundle-1 Bundle
DCH-MessageHeader-1 Event-MessageHeader-1
CareConnect-Organization-1 CareConnect-Organization-1
DCH-HealthcareService-1 CareConnect-HealthcareService-1
CareConnect-DCH-Patient-1 CareConnect-Patient-1
CareConnect-DCH-Emergency-Encounter-1 CareConnect-Encounter-1
CareConnect-Location-1 CareConnect-Location-1
CareConnect-DCH-EmergencyCare-Procedure-1 CareConnect-Procedure-1
DCH-RelatedPerson-1 CareConnect-RelatedPerson-1
DCH-ProfessionalComment-Communication-1 CareConnect-Communication-1
Tags: fhir

All content is available under the Open Government Licence v3.0, except where otherwise stated