Transaction
Each folder must contain at least one transaction. A transaction is related to the patient that is included within the parent folder. A transaction has also a defined author, which must be a healthcare professional (represented by an appropriate hcparty).
A transaction is composed of the following elements.
confidentiality |
To restrict the access to the content of the transaction to some healthcare parties. |
Optional |
id |
Identifies the transaction within the current folder. The ID-KMEHR identifying system requires using the sequential position of the transaction within the folder. In addition to this, local folder identifiers may be used. |
Mandatory |
cd |
Specifies the ‘type’ of the transaction according to the CD-TRANSACTION dictionary. Other local codifications may be associated. |
Mandatory |
date |
In general, this refers to the moment of the medical event that is reported. However, other interpretations may exist. Please consult the description of the transaction determined by the cd element value. |
Mandatory |
time |
In general, this refers to the moment of the medical event that is reported. However, other interpretations may exist. Please consult the description of the transaction determined by the cd element value |
Mandatory |
author |
The author endorses the medical responsibility of the content of the transaction. It must identify at least one physical person. In addition, it can also identify its medical specialty and/or organization. |
Mandatory |
redactor |
The redactor identifies the context of transcription or generation of the content of the transaction. It can identify a physical person like a secretary, nurse, ... and possibly its department and/or organization. It could also represent a robot for automatic content generation, an application for example. The exact requirements will depend on the transaction definition. |
Optional |
iscomplete |
Specifies if the transaction is complete. |
Mandatory |
isvalidated |
Specifies if the transaction is validated. |
Mandatory |
expirationdate |
Expiration date of the transaction (e.g. of a prescription) |
Optional |
heading |
Organizes the content of a transaction in sections, paragraphs. May be decomposed in further headings and or items. Headings should only be used for ‘presentation purposes’. However, other interpretations may exist. Please consult the description of the transaction determined by the cd element value |
Optional |
item |
Represents atomic medical information (or other required information type) |
Optional |
text |
Unstructurated medical content |
Optional |
lnk |
To establish link(s) with the transaction. |
Optional |
recorddatetime |
Date of recording of the transaction. |
Optional |
version | Version of the transaction | Optional |
XML example
The following transaction element is the first transaction of the current folder of the message. It is a transaction corresponding to a ‘sumehr’.
<transaction> <id S="ID-KMEHR" SV="1.0">1</id> <cd S="CD-TRANSACTION" SV="1.0">sumehr</cd> <date>2006-05-20</date> <time>00:57:59</time> <author> <hcparty> <id S="ID-HCPARTY" SV="1.0">14296612004</id> <cd S="CD-HCPARTY" SV="1.0">persphysician</cd> <firstname>Johan</firstname> <familyname>Brouns</familyname> </hcparty> </author> <iscomplete>true</iscomplete> <isvalidated>true</isvalidated> <item> … </item> … </transaction>