Mother and Pregnancy Data within a Neonatal Episode

Background

Within the native BadgerNet Care Record, each Neonatal Care Episode contains its own instance of the following data item groups:

Baby demographics
Mother basic demographics
Father basic demographics
Mother pregnancy and labour/delivery details

When a baby has more than one neonatal care episode, then all these data item groups are usually copied between each neonatal episode record, thereby duplicating them.

Within the BadgerNet Spine model, this data separation between neonatal care episodes remains so as to align with its underlying raw BadgerNet Care Record.

A Spine Client System, with given permissions, can UPDATE any of these data item groups for a single neonatal episode only.

Using the patient/$everything endpoint…

GET [baseUrl]/Patient/{childepisode-logical-id}/$everything

… the Spine will return a merged version of a single baby’s demographics and also a merged version of mother, father, and pregnancy details from all the neonatal care episodes stored for that single baby.

End-Points Summary

CODE

GET [baseUrl]/Patient/{childepisode-logical-id}/$everything

READ ONLY - get all details from all BadgerNet Care Episodes with all repeating episodic details merged into one structure using the LogicalID of ANY of that Child’s BadgerNet Episodes.

CODE

POST [baseUrl]/EpisodeOfCare/{episode-logical-id}/$update-episode

WRITE - Updates any part of a single child’s care episode. This includes all static data items for that single episode.

CODE

POST [baseUrl]/EpisodeOfCare/{episode-logical-id}/mother/$update

WRITE - Updates only the mother part of a neonatal episode’s care record. This includes:

Mother’s key demographics
Pregnancy details
Labour / deliver details

No baby details should be given in the bundle and no father’s details should be given in this bundle.

The mother’s key demographics (name, contact details, etc.) are duplicated in both this single [patient] resource for the mother and also a single [relatedPerson] resource in the respective baby record.

CODE

GET [baseUrl]/Patient/{childepisode-logical-id}/mother/$everything

READ ONLY - get all mother details from all BadgerNet Care Episodes with all repeating episodic details merged into one structure using the LogicalID of ANY of that Child’s BadgerNet Episodes.

CODE

GET [baseUrl]/EpisodeOfCare/{childepisode-logical-id}/mother/$everything

READ ONLY - get all mother details from a single neonatal care episode only. The logical-id given MUST be for a single NNU Care Episode in BadgerNet.

Notes:

Father’s details are limited and so are held entirely in a single [RelatedPerson] resource in the baby.nnu record.

BadgerNet Spine Patients

This is a list of all single patient FHIR records produced by the BadgerNet Spine and their context.

FHIR Resource	BadgerNet source	Resource ID source
patient	Single pregnancy record from BadgerNet Maternity System	Entity ID GUID for mother.preg
patient	Single baby birth record from BNet Maternity System	Entity ID GUID for a single baby.birth
patient	Single neonatal care episode from BNet Neonatal	Entity ID GUID for a single baby.nnu
patient	Merged multi-episode FHIR record that includes ALL birth and paediatric episode details but merges repeating static data.	No logical ID for any run-time-merged patient resource. Use the ‘link’ element to list all the single patient logical IDs that make up the merged result.
patient	Mother's details from the pregnancy part of a NNU care episode record from BNet Neonatal	Entity ID GUID for a single baby.nnu + “mother”.
patient	Merged multi-episode FHIR record that includes mother-only details from all neonatal-only care episodes but merges repeating static data for that mother.	No logical ID for any run-time-merged patient resource. Use the ‘link’ element to list all the single patient logical IDs that make up the merged result.