2437 résultats

Header

BASIC, STANDARDS

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.

Heading

BASIC, STANDARDS

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.

Item

BASIC, STANDARDS

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).

Folder

BASIC, STANDARDS

Each kmehrmessage must contain at least one folder. A folder corresponds to a patient. It may contain several transactions concerning the patient.

Transactions

BASIC, STANDARDS

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.

ehValidator Tool Work-in-Progress

BASIC, STANDARDS

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.

FAQ Kmehr Migration Formats & Validation Tool

BASIC, STANDARDS

Back to parent

Basic

BASIC, STANDARDS

KMEHR messages are XML messages. Those messages have to be valid with regard to a general XSchema. This XSchema is the core element of the KMEHR norm.

GP Patient Migration Format

BASIC, STANDARDS

Status: Draft

GP Software Migration Format

BASIC, STANDARDS

Status: Published