Condition-BNet-Child-NNConditions

FHIR Resource information

FHIR Resource	🌍Condition-BNet-Child-NNConditions. Based on 🌍 Condition
Description	Neonatal conditions
Release status	NOT AVAIL. (RFC)
Cardinality	tbc
Writing to Spine permitted	YES - for Spine Client Type (NNU-SYSTEM) Should be sent to Spine if available.
Spine filters	None

Key FHIR Resource elements used

* id - Unique resource identifier

Summary	Unique resource identifier
Mandatory	Yes
Expected type	🌍string
Write allowed	No
Data Dictionary item	None

* code - Identification of the condition, problem or diagnosis

Summary	Identification of the condition, problem or diagnosis
Mandatory	Yes
Expected type	🌍codeableConcept
Write allowed	Yes
Data Dictionary item	None
Value set used	🌍ValueSet-BNet-Child-NNConditions

bodySite - Anatomical location, if relevant

Summary	Anatomical location, if relevant
Mandatory	No
Expected type	🌍codeableConcept
Write allowed	Yes
Data Dictionary item	None
Value set used	🌍ValueSet-BNet-Child-NNConditionBodySite

onsetDateTime - Estimated or actual date or date-time

Summary	Estimated or actual date or date-time
Description	The expected format for this element is YYYY-MM-DD or YYYY-MM-DDThh:mm:ss+zz:zz, depending on the condition being communicated.
Mandatory	No
Expected type	🌍dateTime
Write allowed	Yes
Data Dictionary item	None

abatementDateTime - When in resolution/remission

Summary	When in resolution/remission
Description	The expected format for this element is YYYY-MM-DD or YYYY-MM-DDThh:mm:ss+zz:zz, depending on the condition being communicated.
Mandatory	No
Expected type	🌍dateTime
Write allowed	Yes
Data Dictionary item	None

note - Additional information about the Condition

Summary	Additional information about the Condition
Mandatory	No
Expected type	🌍string
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