GP Software Migration Format
General information
Status: Published
Version: 2.0
Last update: 2013-10-17
Purpose
The 'GP Software Migration Format' aims to define an export/import format enabling GP medical software to migrate the complete medical record of one or more patients from one software application to another software application for the same GP.
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 'gpsoftwaremigration'. |
Transactions
The following transactions from CD-TRANSACTION must be used to compose a 'GP Software 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. |
| pharmaceuticalprescription | 0-* | A pharmaceutical prescription aims to prescribe any pharmaceutical or other complementary product and material |
Example
A complete example of a 'GP Software Migration Format' file is available here.