GP Patient Migration Format
General information
Status: Draft
Version: 1.0
Last update: 2013-07-29
Purpose
The ‘GP patient migration format’ aims to define an export/import format enabling GP medical software to export a medical record of one patient from the software application of one GP to the software application of another GP. It thus specializes the KMEHR general message structure in order to fit with this purpose.
Header
Besides the usual header definition, the header must respect the following specific rules.
| standard | The standard value of CD-STANDARD must be higher than ‘20110701’. It must also contain the optional element ‘specialisation’ with the value 'gppatientmigration'. |
Transactions
The following transactions from CD-TRANSACTION must be used to compose a 'GP Patient Migration Format' message, according to the given cardinalities.
| clinicalsummary | 1-1 | Mainly contains a summary of the clinical items of the patient record. |
| labresult | 0-* | Laboratory results received by the GP for the patient (if the data are stored in an internal format, the result should be exported as a plain text - as long as there is no lab semantic standard mandatory). |
| result | 0-* | Results of the other technical examinations such as RX reports (if the data are stored in an internal format, the result should be exported as a plain text – as long as there is no semantic standard mandatory). |
| note | 0-* | Received and sent correspondence related to the patient. |
| contactreport | 0-* | A contact report should be established for each contact with the patient. This transaction is a specialization of the standard 'contactreport' transaction, customized to fit with the specific rules required for the SMF. |
Items
Some specific rules apply to items in a ‘patient migration file’:
• Items with the status ‘isrelevant=false’ should not be present in a PMF
Example
A complete example of a 'GP Patient Migration Format' file is available here.