The migration formats aim to define a series of export/import formats enabling medical software to migrate medical content from one software application to another software application without loss of information.
We describe here a specialization of the standard 'contact' transaction. The contact report documents a consultation, emergency visit, home visit, ...
This is the string that uniquely identifies a KMEHR element: a message(header), a folder, a transaction, a heading or an item.
The header is the first part of a KMEHR message. It is mandatory. It mainly identifies the sender and the receiver of the message as well as the message itself.
Headings allow one to organize a transaction within sections, paragraphs. They may be decomposed in further headings and or items. Headings should only be used for ‘presentation purposes’. However, some transactions may require a specific heading decomposition. A heading may be composed of headings, items, texts or links. A heading must contain at least one of those elements.
The item element corresponds to the atomic medical information (e.g. blood pressure). It can also represent a concept that is not medical if required (e.g. a contact person).
Each kmehrmessage must contain at least one folder. A folder corresponds to a patient. It may contain several transactions concerning the patient.
This page provides an overview of the ‘recognized’ transactions. By ‘recognized’, we mean that the ‘type’ of the transaction element belongs to the table CD-TRANSACTION.
The SumEHR/SMF/PMF Validator Tool is a small local application that is intended to perform more advanced syntactic validation of the KMEHR transactions "Sumehr" en "GP Software Migration Format" than the one made possible by the KMEHR grammar defined using the KMEHR XSD.