Allergy (Patient Dossier)
1.0.1 - STU1

This page is part of the HL7 Belgium FHIR Implementation Guide - Allergy profiles (v1.0.1: Trial Use) based on FHIR R4. The current version which supercedes this version is 1.1.0. For a full list of available versions, see the Directory of published versions

Artifacts Summary

Contents:

This page provides a list of the FHIR artifacts defined as part of this implementation guide.

Structures: Logical Models

These define data models that represent the domain covered by this implementation guide in more business-friendly terms than the underlying FHIR resources.

Allergy Intolerance Logical Model

Allergy / Intolerance information model

Structures: Resource Profiles

These define constraints on FHIR resources for systems conforming to this implementation guide

BeAllergyIntolerance

Belgian federal profile for an allergy and/or an intolerance. Initially based on the functional description of the NIHDI.

Terminology: Value Sets

These define sets of codes used by systems conforming to this implementation guide

BeAllergyIntoleranceCode

Codes as communicated by NIHDI and the FOD Terminology Center differentiating types of allergy intolerance codes. This valueset supports the Belgian federal FHIR profiling effort.
BeCausativeAgent

Causative Agents for Allergy (non medication)
be-exposureroute

Codes to illustrate differentiating types of exposure route. This valueset supports the Belgian federal FHIR profiling effort.
be-noallergy

Codes as communicated by the FOD Terminology Center differentiating types of no allergies. This valueset supports the Belgian federal FHIR profiling effort.
be-riskmanifestation

Codes as communicated by NIHDI and the FPS Terminology Center differentiating types of risk manifestation. This valueset supports the Belgian federal FHIR profiling effort.

Terminology: Naming Systems

These define identifier and/or code system identities used by systems conforming to this implementation guide

BeNSAllergy

Unique Identifier for Allergies in the Belgian Health Landscape

Example: Example Instances

These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like

allergyintolerance1
allergyintolerance2
allergyintolerance3
example
practitioner
relatedperson
terminology-expansion