Spine Client: MAT-RO
Introduction
Generic Spine Client System instance that performs read-only queries to get pregnancy summary data items.
It is assumed that the Spine Client System has only the National ID and Date of Birth for a patient available to identify a single patient.
The set of FHIR resources returned depends on the Spine Record Filter that is assigned to each Spine Client System instance.
Spine Client System assumptions/requirements
The system has the associated patient’s National ID and DOB available as the key for data queries.
The system can perform a two-hit query, i.e.
Step 1: Find all pregnancies for a single woman
Step 2: Get single pregnancy data
The system is secure by national health service standards and is authorised by all participating BadgerNet Care Locations to have read-only access to their respective pregnancy care records.
Basic use case
To get pregnancy data FHIR resources, the Spine Client System must perform a two-step process.
Step 1: Get a pregnancy record index
Send a request to the Spine to identify the patient using the patient’s national ID and DOB. This is done using the $find-all-pregnancies API command.
The BadgerNet Spine will determine which pregnancy records you are allowed to access.
For each pregnancy record allowed, a Summary FHIR resource will be included in the resulting bundle. Each [patient] resource returned represents a single BadgerNet Pregnancy record and each will have an associated unique Logical ID. It is this ID that is then used to get the details for the required pregnancy in subsequent requests.
Step 2: Get the pregnancy data items
Using the Logical ID from the required [patient] resource given in step one, query the Spine using this ID to return a full FHIR Bundle that contains all FHIR Resources for that pregnancy as defined in the Spine Record Filter for your associated project. This is done using the $everything API command.