The FHIR profiles used for the Baby details (person) List

Heading Description

Birth details of the baby.

The following FHIR profiles are used to form the Baby Details (person) details list structure:

The following profiles are referenced from the Baby Details (person) details list structure:

Baby Details (Person) Structure

Page-1 Dynamic connector.2668 Patient Resource (baby) Patient Resource (baby) PatientResource(baby) ProcedureRequest Resource ProcedureRequest Resource ProcedureRequestResource Dynamic connector.2674 0..* R entry.item 0..* R entry.item 0..* Rentry.item 0..* R subject 0..* R subject 0..* Rsubject 0..* R subject 0..* R subject 0..* Rsubject Baby Details (Person) List Resource Baby Details (Person) List Resource Baby Details (Person)List Resource 1..1 M subject 1..1 M subject 1..1 Msubject Reference to Patient resource Reference to Patient resource Reference to Patient resource Dynamic connector.1542 Observation Resource Observation Resource ObservationResource Dynamic connector.1001

Maternity Data Standards Mapping to FHIR profiles

Mapping Overview

Data Standard Element FHIR Profile Mapping FHIR Element
Family Name Patient name.family
First Given Name Patient name.given
Other given names (s) Patient name.given
NHS Number Patient identifier.nhsNumber
Local Patient Identifier Patient identifer
Phenotypic Sex (Baby) Observation code and value
Birth Order Patient multipleBirthInteger
Number of Births in confinement Observation code and value
Birth Weight Observation code and value
Locally calculated birth weight centile Observation code and value
Length of Gestation at Birth Observation code and value
Still Born Indicator Observation code and value
Rhesus Status Observation code and value
Suspected Congenital Abnormality Indicator Observation code and value
Investigations Requested ProcedureRequest code

The following tables detail how to populate the FHIR resources and the mapping to the Maternity data standard.

Mapping for Baby Details (Person) List

> Level 1 List Resource > Level 2 CareConnect-List-1 > Level 3 None
View Used FHIR Elements View All FHIR Elements

Patient Reference

The Baby Details (Person) list has a mandated subject reference to the Patient resource. This means that any exchange of the Baby Details (Person) heading data must also include the Patient demographics List.

Mapping for Patient Resource (baby)

> Level 1 Patient Resource > Level 2 CareConnect-Patient-1 > Level 3 None
View Used FHIR Elements View All FHIR Elements

Mapping for ProcedureRequest Resource

> Level 1 ProcedureRequest Resource > Level 2 CareConnect-ProcedureRequest-1 > Level 3 None
View Used FHIR Elements View All FHIR Elements

Mapping for Observation Resource

The following Observation codes and value data types should be used for the Observations for the Baby Details (Person) structure:

Observation Code Value[x]
Phenotypic Sex (Baby) TBC CodeableConcept:
A snomed code from ^999002891000000103:Person phenotypic sex findings simple reference set (foundation metadata concept)
Number of Births in confinement TBC Quantity
Birth Weight Snomed CT: 364589006 - Birth weight (observable entity) Quantity
Locally calculated birth weight centile Snomed CT: 301334000 - Birth weight centile (observable entity) Quantity
Length of Gestation at Birth Snomed CT: 412726003 - Length of gestation at birth (observable entity) Quantity
Still Born Indicator TBC CodeableConcept:
A Snomed code from <302080006:Finding of birth outcome (finding)
Rhesus Status TBC CodeableConcept:
A Snomed code of ‘165747007 - RhD positive (finding)’ or ‘165746003 - RhD negative (finding)’
Suspected Congenital Abnormality Indicator Snomed CT: 1097291000000101 - Suspected congenital abnormality (situation) Boolean
> Level 1 Observation Resource > Level 2 CareConnect-Observation-1 > Level 3 None
View Used FHIR Elements View All FHIR Elements
Name Card. Conformance Type Description, Constraints and mapping for Digital Maternity Implementation
Observation     Measurements and simple assertions
Constraint (dom-2): If the resource is contained in another resource, it SHALL NOT contain nested Resources
Constraint (dom-1): If the resource is contained in another resource, it SHALL NOT contain any narrative
Constraint (dom-4): If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated
Constraint (dom-3): If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource
Constraint (obs-7): If code is the same as a component code then the value element associated with the code SHALL NOT be present
Constraint (obs-6): dataAbsentReason SHALL only be present if Observation.value[x] is not present
- id 0..1 Optional Id Logical id of this artifact
- meta 0..1 Mandatory Meta Metadata about the resource
The value attribute of the profile element MUST contain the value 'https://fhir.hl7.org.uk/STU3/StructureDefinition/CareConnect-Observation-1'
- status 1..1 Mandatory Code registered : preliminary : final : amended +
Binding (required): Codes providing the status of an observation. ObservationStatus
This MUST contain the value 'final'
- code 1..1 Mandatory CodeableConcept Type of observation (code / type)
Binding (example): Codes identifying names of simple observations. LOINC Codes
This MUST contain the value specified for the relevant Observation specifed in the table above
- - coding 0..* Required Coding Code defined by a terminology system
Slicing: Discriminator: code, Ordering: false, Rules: Open
- - coding (snomedCT) 0..1 Mandatory Coding Code defined by a terminology system
Binding (extensible): A code from the SNOMED Clinical Terminology UK coding system describing a type of observation CareConnect-ObservationType-1
This MUST contain the value specified for the relevant Observation specifed in the table above
- - - system 1..1 Mandatory Uri Identity of the terminology system
The element MUST contain the value 'http://snomed.info/sct'
- - - code 1..1 Mandatory Code Symbol in syntax defined by the system
- - - display 1..1 Mandatory String Representation defined by the system
- subject 0..1 Mandatory Reference Who and/or what this is about
Constraint (ref-1): SHALL have a contained resource if a local reference is provided
This MUST reference the Patient that is the subject of the Observation
    Mandatory CareConnect-Patient-1  
- - reference 0..1 Optional String Literal reference, Relative, internal or absolute URL
- - identifier 0..1 Optional Identifier Logical reference, when literal reference is not known
- - display 0..1 Optional String Text alternative for the resource
- value[x] 0..1 Optional Quantity Actual result
Constraint (qty-3): If a code for the unit is present, the system SHALL also be present
This MUST use the value datatype specified for the relevant Observation specifed in the table above
    Optional CodeableConcept  
    Optional String  
    Optional Boolean  
    Optional Range  
    Optional Ratio  
    Optional SampledData  
    Optional Attachment  
    Optional Time  
    Optional dateTime  
    Optional Period  

Baby Details (Person) Heading Example

Tags: fhir