Spine Project - NZ Maternity
Introduction
The BadgerNet NZ Perinatal Spine system provides an interoperability service between the existing national BadgerNet Live Perinatal Care Record and authorised third-party patient data management systems.
The national BadgerNet System currently provides the NZ perinatal clinical community with a live single care record platform for pregnancy and newborn care for all of NZ. This is currently in live use in four District Health Boards (DHB) and also for the Midwifery and Maternity Providers Organisation (MMPO) users.
In addition to the current BadgerNet System, various third-party community-based maternity care record systems are in use throughout NZ. Using standards-based and secure API methodologies, the BadgerNet Spine aims to provide access for authorised third-party system providers to share live pregnancy care record information with the national BadgerNet System’s single pregnancy record.
Key project goals
Provide both read and write access to a national single pregnancy care record for NZ for authorised non-BadgerNet systems.
Create a full FHIR model for the complete HISO2 Maternity Data Set to be used as the foundation for pregnancy care record reading and updating.
Extend the detail of the pregnancy and newborn care record over time to allow a more granular exchange of live care record details.
Project Phases
Phase one | Initial go-live of platform. Key demographics and pregnancy booking details. |
|---|---|
Phase two | Labour and Birth |
Phase three | Postnatal Baby |
Phase four | Previous Pregnancies |
On-going | Linked to national BadgerNet System Update cycle (every 8 weeks), continue to extend and mature the FHIR modelling available on the Spine platform. |
MoH Spine Client Vendor requirements
Validation process / paperwork TBC
Maternity Spine Client technical requirements
Each single instance of a vendor's system implementation must have its own specific BadgerNet Spine Client ID and associated secret. Initially (Project phase one), this will be created and managed by Clevermed, but when the Vendor Administration Tool is available, this will subsequently be managed by each vendor going forward.
All Spine transactions occur over the Internet. As such, all Client System must have http internet access at runtime. See: https://clevermed.atlassian.net/wiki/spaces/CDL/pages/1350008918/Technical+summary#End-points
Full and detailed transactional audit trail should be a feature of each vendor’s system solution for medico-legal purposes.
Spine Client details required
The BadgerNet Spine platform requires the following information for each distinct Spine Client System instance:
Full instance name (if this client system instance is used by just one person, then this name should include their name) e.g. “Acme Solutions instance 1234 for Betty Jones”.
Contact address, email, and telephone number.
Community Midwife Care Location setup
The national BadgerNet Maternity system is dependant on the knowledge of where care is provided and by whom.
As such, before any NZ community midwifery practice can use the BadgerNet Spine to submit data to be saved in the BadgerNet single pregnancy record, we need to ensure we have the details of the midwifery practice and its associated midwife team.
In a BadgerNet context, each midwifery practice is recorded as a BadgerNet Care Location.
For each Care Location we need the following details:
Practice name
Key contact details (name, email, telephone)
Principle contact address
IT Contact person
IT System (Vendor) used for pregnancy care records
National organisation codes
Midwife details
When setting the new Lead Midwife for a pregnancy record, a full FHIR resource for [NZPractitioner] should be submitted as part of the FHIR bundle. See Lead healthcare professionals for pregnancy
As such, each Vendor’s system should be able to populate this resource and this must include the NZ CPN ID.