2375 résultats

Temporality

TABLES, STANDARDS

This is the temporality status of an item. Those codes are derived from EMDMI - EPR Structuration.

Context of use: temporality element (item)

Frequently Asked Questions

BASIC, STANDARDS

During the development phase we receive multiple questions from the people that implement the new releases in their projects, and we strive to respond to them as fast and as clear as possible. Where the questions and responses are applicable to other partners or situations, we decided to start this FAQ section in order to share that knowledge.

Migration formats

BASIC, STANDARDS

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.

Contact report (MF)

BASIC, STANDARDS

We describe here a specialization of the standard 'contact' transaction. The contact report documents a consultation, emergency visit, home visit, ...

KMEHR identifier

BASIC, STANDARDS

This is the string that uniquely identifies a KMEHR element: a message(header), a folder, a transaction, a heading or an item.

Basic data types

BASIC, STANDARDS

KMEHR makes use of usual XSchema literals such as xsd:boolean, xsd:decimal and xsd:nonNegativeInteger.

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.

Résultats de 301 à 310 de 2375