Encounter-BNet-Child-NeonatalUnitAdmission

FHIR Resource information

FHIR Resource	🌍Encounter-BNet-Child-NeonatalUnitAdmission. Based on 🌍 Encounter
Description	Neonatal Unit admission event
Release status	NOT AVAIL. (RFC)
Cardinality	Multi instance on date
Writing to Spine permitted	YES - for Spine Client Type (NNU-SYSTEM)
Spine filters	NNU-DETAIL

Key FHIR Resource elements used

subject - Reference back to root child patient resource. The root patient resource should have an ID of $“Patient/{LogicalID}”

Summary	Reference back to root child patient resource. The root patient resource should have an ID of $“Patient/{LogicalID}”
Mandatory	No
Value type	🌍Reference(Patient)
Write allowed	Yes
Data Dictionary item	None

period.start - Date and time of the AdmissionTime to the neonatal unit

Summary	Date and time of the AdmissionTime to the neonatal unit
Mandatory	No
Expected type	🌍dateTime
Write allowed	Yes
Data Dictionary item	PaediatricEpisodeStart - Paediatric episode start - Topic: (ChildAdmissions) Child care episode ADT - Topic: (NNU-Admission) Details of a single admission to a neonatal unit

period.end - Date and time of the discharge or death from the neonatal unit

Summary	Date and time of the discharge or death from the neonatal unit
Mandatory	No
Expected type	🌍dateTime
Write allowed	Yes
Data Dictionary item	PaediatricEpisodeEnd - Paediatric episode end - Topic: (ChildAdmissions) Child care episode ADT - Topic: (NNU-Admission) Details of a single admission to a neonatal unit

serviceProvider - Reference to the BadgerNet care location for the Neonatal Unit

Summary	Reference to the BadgerNet care location for the Neonatal Unit
Mandatory	No
Value type	🌍Reference(Organization)
Write allowed	Yes
Data Dictionary item	None

hospitalization.origin - The BadgerNet Care Location, if known, where the baby was admitted from

Summary	The BadgerNet Care Location, if known, where the baby was admitted from
Mandatory	No
Value type	🌍Reference(Organization)
Write allowed	Yes
Data Dictionary item	None

hospitalization.dischargeDisposition - Category or kind of location after discharge

Summary	Category or kind of location after discharge
Mandatory	No
Expected type	🌍codeableConcept
Write allowed	Yes
Data Dictionary item	None
Value set used	🌍ValueSet-BNet-Child-NNDischargeDisposition

hospitalization.destination - Where the patient is discharged to

Summary	Where the patient is discharged to
Description	This element is only required when the element hospitalization.dischargeDisposition is set to 306699001.
Mandatory	No
Value type	🌍Reference(Organization)
Write allowed	Yes
Data Dictionary item	None

* status - Status of the encounter

Summary	Status of the encounter
Mandatory	Yes
Expected type	🌍code
Write allowed	Yes
Data Dictionary item	None
Value set used	🌍ValueSet-BNet-Child-NNEncounterStatus

* episodeOfCare - Reference to the episode of care

Summary	Reference to the episode of care
Mandatory	Yes
Expected type	🌍reference
Write allowed	Yes
Data Dictionary item	None

Example JSON when WRITING to the Spine

Example JSON pending, awaiting development.

Example JSON when READING from the Spine

Example JSON pending, awaiting development.

CONFIDENTIAL/COMMERCIAL IN CONFIDENCE

Confidentiality/document control

This document contains information that is confidential to System C Healthcare Ltd (System C) and is intended for our customers to use in connection with our products and services. It must not be used for any other purpose nor disclosed to any other party, either whole or in part, without the prior written consent of System C except as follows. A customer may permit those of its employees, advisors and agents having a need to know the contents of this platform to have access to such of the contents as are strictly necessary, but that customer shall ensure that such employees, advisors and agents are bound to it by an obligation, in similar term, to keep it confidential. A customer's acceptance of these obligations shall be indicated by that customer's use of any of the information contained in this document.

System C acknowledges that a customer may be bound by the Freedom of Information Act 2000 (FOIA). In such cases, System C considers that the contents of this document are confidential and exempt from disclosure pursuant to section 41 of the FOIA. A customer should consult System C before making any disclosure of information relating to System C under the FOIA. System C's business information, methodologies, solutions, as well as reference to System C clients and their projects, are always considered by System C to be exempt from disclosure by virtue of section 41 and 43 of the FOIA, whether indicated or not. 

Product Information: any descriptions of future functionality reflect current product direction, are for informational purposes only, and do not constitute a commitment to provide specific functionality. Timing and availability remain at System C’s discretion and are subject to change and applicable regulatory approvals.

Warning: Paper or PDF copies of this document are not version controlled and will automatically be considered obsolete and superseded at the time of printing or conversion.

Confidentiality/document control statement version number 2.0, QMSUID-0059