2376 resultaten

New message guidelines

BASIC, STANDARDS

Please be aware any FHIR project shall follow the FHIR governance that is described on its own page

Patient

BASIC, STANDARDS

The patient element aims to represent patients. It thus corresponds to an open structure- very few elements are mandatory- that gathers common (administrative) attributes of physical persons.

Transaction

BASIC, STANDARDS

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

HCparty

BASIC, STANDARDS

The hcparty element is a generic element that aims to represent any kind of healthcare party: organization, physician, medical specialty or even IT systems.

ehValidator

BASIC, STANDARDS

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.

FHIR profiles

STANDARDS

If you are looking for the work-in-progress concerning FHIR laboratory, please consult our laboratory IG.

OID overview

STANDARDS

Some messages use OIDs: unique object identifiers. Mostly to refer to a system or organization that itself uses its own codes to identify its elements or members.

Tutorial/Case study

BASIC, STANDARDS

The tutorial explains, step by step, the KMEHR message structure, using a simple case study.

Guided tour

BASIC, STANDARDS

 

Schematron

BASIC, STANDARDS

To help developing parties to implement message specifications, eHealth platform provides Schematron files.