User initiated encounter
The use-case for sending information about a user initiated digital-encounter to be added as a journal entry in the EHR. A journal note is reated and recorden in the EHR using a digital-Encounter resource. The user can enter additional information in the Encounter.note element, the signature of the user (Name and username) should always be recorded in the Encounter.signature element.
Sensor alarm resolved
The sensor reports a digital encounter. If the service provider thinks this encounter and the resoultion of the event is necessary to record in the EHR, a journal note is created and recorded in the EHR using a digital-Encounter resource. The user can enter additional information in the Encounter.note element. The the signature (Name and username) of the user should always be recorded in the Encounter.signature element.
A note about classHistory
In some cases the user reporting digital-Encounter events to the EHR could choose to resolve a number of reported alarms or use the sensor in multiple ways in order to resolve the case. When the user resolves multiple sensor alarms or initiates multiple sensor events as part of one encounter, the system is expected to report a single digital-Encounter resource to the EHR containing a classHistory element to document all the alarms or user initiated digital-Encounters.
API parameters and return values
The VKP expects to receive a POST interaction containting a vkp-digital-Encounter resource. The VKP is expected to record this information in the EHR and return an operation outcome.
Usage of profile attributes
The following table summarizes the fields that are important for use in the VKP APIs when sending information to VKP.
|note||A journal note to document the digital encounter.|
|signature||Signature for the journal note|
|device||The device(s) used in the patient encounter. For example, a particular camera device (deviceIdentifier, display, type, typeName)|
|device.deviceIdentifier||Identifier of the device|
|device.display||Human readable name / displayname of the device|
|device.type||Generic type of the device, such as Trykknapp, Snortrekk etc.|
|device.typeName||Specific typename / make / model of the device|
|class||Specifies the kind of encounter that is reported (image, speech etc.), according to class-codes.|
|classHistory||When the user resolves multiple sensor alarms or initiates multiple sensor events as part of one encounter, the system is expected to report a single digital-Encounter resource to the EHR containing a classHistory element to document all the alarms or user initiated digital-Encounters.|
|type||Specifies whether this reports an encounter, an alarm/event or both, according to type-codes.|
|subject||The patient or group that is the subject of the encounter|
|participant||List of participants, usually usually health care providers, involved in the encounter|
|period||The period when the encounter took place.|
|reason||Specifies the reason why this encounter took place (either a type of event or empty if this was a planned encounter), according to event-codes.|
|location||The general location of the patient (such as the residence or institution).|