2473 résultats

KMEHR 1.38 released

ARTICLE STANDARDS: 14/04/2023

Dear stakeholder/client/developer,...

A new version of the KMEHR schema has been released: version 1.38.

Healthcare Party Type

TABLES, STANDARDS

Value identifies the type of health care party. Three main categories are covered: persons, organisations and medical specialities.

Context of use: hcparty element.

KMEHR 1.37 released

ARTICLE STANDARDS: 01/10/2022

Dear stakeholder/client/developer,...

A new version of the KMEHR schema has been released: version 1.37.

New values in CD-VACCINEINDICATION: 'pneumonia15', 'pneumonia20'

A new version of the EhValidator has been released

ARTICLE STANDARDS: 21/09/2022

The version 1.10 of the Incapacity Notification Schematron has been added to the EhValidator.

Incapacity Notification 2.0 Schematron has been modified.

ARTICLE STANDARDS: 20/09/2022

Following the Incapacity Notification 2.0 Clarifications from 2022-16-09, we have adapted the Schematron by removing some contraints.

See these tickets to view the changes: ESi-93 ESI-42 ESI-72

Laboratory result

TRANSACTIONS, STANDARDS

The Laboratory result transaction aims to transfer the results of examinations performed by the following medical specialties: laboratory, anatomopathology, genetics, bacteriology, molecular biology and toxicology. Results from a clinical investigation should be reported through the transaction Contact report. Results from other technical tests are reported through the transaction Laboratory result.

Medication Scheme Element

TRANSACTIONS, STANDARDS

Please note the transactions ‘medicationscheme’, ‘medicationschemeelement’ and ‘treatmentsuspension’ shall be considered as a whole.

Treatment Suspension

TRANSACTIONS, STANDARDS

Please note the transactions ‘medicationscheme’, ‘medicationschemeelement’ and ‘treatmentsuspension’ shall be considered as a whole.

Medication Scheme

STANDARDS

Please note the transactions ‘medicationscheme’, ‘medicationschemeelement’ and ‘treatmentsuspension’ shall be considered as a whole.

Technical fix in BePatient FHIR Profile

ARTICLE STANDARDS: 17/06/2021

Dear stakeholder/client/developer,...

A technical issue was detected with the published BePatient FHIR profile that could impact certain implementations when integrating the core federal set of FHIR profiles. The binding level to the correct valueset to express a contact.relationship was defined on a structural level too high which could cause problems in certain scenarios.

This has been fixed.

The version of the BePatient artefact went hereby to 1.0.1 and is integrated in our 1.2.2 package.

As always you can find the link to the concrete FHIR artefacts via our federal profiles FHIR page.

Résultats de 1681 à 1690 de 2473