Profile for Submit Communication Alert API

This profile is a bundle resource that is used to hold 1 or 2 entries: Communication and Observation (optional) resources, for the sending of communication alerts together with the vital signs readings (if applicable) in a single transaction (See API - Submit Communication Alert).

The Communication resource defines the communication alert for the remote clinical monitoring of the patient. Details like the type of alert (See RCM Communication Alert Codes) and the patient id will be used. The observation id will also be stored depending on the alert code (i.e "Threshold" and "Missed Read").

The Observation resource defines the vital signs readings of the patient. Details like the type of vital signs (i.e blood pressure), the readings for each vital sign (i.e systolic blood pressure, diastolic blood pressure), the device guid that took the readings and the subject patient id will be stored.

In the event the readings are missed, the effective period will be used to store the start and end date of the missed readings with the data absent reason as "unknown".

These are the details for these resources:

Name	Canonical_URL	Status	Version
Command 'link' could not render: Object reference not set to an instance of an object.	http://fhir.synapxe.sg/StructureDefinition/profile-bundle-communication-observation	active	5.0.0
Command 'link' could not render: Object reference not set to an instance of an object.	http://fhir.synapxe.sg/StructureDefinition/profile-communication	active	5.0.0
Command 'link' could not render: Object reference not set to an instance of an object.	http://fhir.synapxe.sg/StructureDefinition/profile-observation	active	5.0.0

Resource content

These are different views on these resources:

Bundle

Command 'tree' could not render: File was not found for BundleCommunicationObservation.StructureDefinition.json

Command 'dict' could not render: File was not found for BundleCommunicationObservation.StructureDefinition.json

Command 'xml' could not render: File was not found for BundleCommunicationObservation.StructureDefinition.json

Command 'json' could not render: File was not found for BundleCommunicationObservation.StructureDefinition.json

Command 'link' could not render: Object reference not set to an instance of an object.

Communication

Command 'tree' could not render: File was not found for Communication.StructureDefinition.json

Command 'dict' could not render: File was not found for Communication.StructureDefinition.json

Command 'xml' could not render: File was not found for Communication.StructureDefinition.json

Command 'json' could not render: File was not found for Communication.StructureDefinition.json

Command 'link' could not render: Object reference not set to an instance of an object.

Observation

Command 'tree' could not render: File was not found for Observation.StructureDefinition.json

Command 'dict' could not render: File was not found for Observation.StructureDefinition.json

Command 'xml' could not render: File was not found for Observation.StructureDefinition.json

Command 'json' could not render: File was not found for Observation.StructureDefinition.json

Command 'link' could not render: Object reference not set to an instance of an object.

Terminology Bindings

These are the terminology bindings within these resources:

Path	Binding Strength	Value Set(Code System)	Description
Bundle.type	Required	BundleType (HL7 FHIR)	Indicates the purpose of a bundle - how it is intended to be used.
Communication.status	Required	EventStatus (HL7 FHIR)	The status of the communication.
Communication.reason.concept	Required	Command 'link' could not render: Object reference not set to an instance of an object.	The communication alert codes used in RCM.
Observation.status	Required	ObservationStatus (HL7 FHIR)	Codes providing the status of an observation.
Observation.category	Required	ObservationCategory (HL7 FHIR)	Codes for high level observation categories.

Constraints

There are no constraints for these resources.