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).
The hcparty element is a generic element that aims to represent any kind of healthcare party: organization, physician, medical specialty or even IT systems.
The ehValidator 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.
The tutorial explains, step by step, the KMEHR message structure, using a simple case study.
In a top-down approach and disregarding the detailed elements and attributes, a message KMEHR may, very roughly, be described as follows
To help developing parties to implement message specifications, eHealth platform provides Schematron files.
The definition of KMEHR is completed by a minimal set of web service operations to support the exchange and the sharing of medical files. Those web services result from concrete implementations initiated throughout the Flows projects. In order to unify the interfaces developed within those local and regional initiatives, a revision of those interfaces has been undertaken within the ‘G19 - Belgian Care Providers Telematic Advisory Group’ in the context of the 'hubs-metahub' architecture. The result of this work is available here. The work currently published has the status of a draft as the definitions must still be validated through effective testing with partners involved in the hub-metahub project. Those tests are currently running. The 'hub-metahub' architecture identifies two sets of web service operations: the operations provided by the hubs to their clients, called 'intrahub webservices', and the web service operations provided by the hubs to the other hubs, called 'interhub webservices'. The functional specification of each operation is available in the table below. The following archive file contains the complete XSD structure corresponding to the payload of the webservices. It also contains the WSDL that defines the interface at the interhub level.
Conditions for re-use (Creative Commons-0 licence)
++ THE PROCESS DESCRIBED ON THIS PAGE IS SUBJECT TO CHANGE! ++