RIZIV-INAMI Patient Record
0.1.0 - CI Build

RIZIV-INAMI Patient Record, published by RIZIV-INAMI. This is not an authorized publication; it is the continuous build for version 0.1.0). This version is based on the current content of https://github.com/hl7-be/riziv-inami/ and changes regularly. See the Directory of published versions

Artifacts Summary

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

Allergy Intolerance

Allergy / Intolerance resources. These artefacts define the constraints and vocabulary necessary to record allergies and intolerances, suspected or confirmed. A few example resources and scenario demonstrate the use of these resources.

AllergyIntolerance Logical Model

Allergy Intolerance Logical Model

AllergyIntolerance

Allergy Intolerance profile

Example Practitioner - Dr Durant (GP)

Dr. Paul Durant (GP)

Example practitioner - Dr Lenoir

Lr François Lenoir

Example Patient - Noel Joyeux

Patient Noel Joyeux

Example - Suspected Allergy

Suspected Allergy to Penicillin

Example - Refuted Allergy

Allergy has been refuted - confirmed as non-existent

Example - Allergy 1 - peanut allergy

Allergy to peanut

Example - Allergy 2 - Pollen allergy

Allergy to pollen

ExampleScenario - Suspected Allergy

Suspected Allergy, then refuted

Patient Will

Patient Will profile and vocabulary. The Patient Will captures a patient’s expressed preferences related to care provision. The Logical Data Model defines the functional data needs. An example demonstrates the use of the profile.

Logical Model Patient Will

Patient Will logical model

Patient Will core BE profile

The Core BE profile for Patient Will

Patient Will Categories

Patient Will Category code system

Patient Will Categories

Patient Will Category value set

Patient Will codes

Patient Will directive code system

Patient Will directives

Patient Will directive value set

Example - Patient Will

Patient Will

Addiction

The profile for Addiction, intended to capture known or suspected substance or other addictions. The Logical Data Model defines the functional data needs. An example demonstrates the use of the profile.

Logical Model Addiction

Addiction record logical model

Addiction BE profile

Belgian Profile to capture Addictions (on substances or others)

Addiction Quantifier extension

Belgian Extension to allow quantification of addictions (on substances or others) - for example 10 packs per week, 1 bottle per day

Example - Patient Smoking addiction

Patient Smoking addiction

Addiction Categories

Addiction Category value set

Addiction Codes

Addiction Code value set

Vaccination

Vaccination related resources. These artefacts define the constraints and vocabulary necessary to record the administration of vaccine administrations, including the reference to a vaccination schema or protocol, and eventual immediate reactions. The Logical Data Model defines the functional data needs. The vocabulary resources help ensure conformity and data consistency. The profile and extensions define the technical specifications. A set of examples demonstrates the use of the profile.

Logical Model Vaccination

Vaccination logical model

Vaccination core BE profile

The Core BE profile for Vaccination (event)

Location of the vaccination event

Location of the vaccination event

CodeSystem - Care location

The location of the care event

CodeSystem - vaccination confirmation status

The list of vaccination confirmation status

CodeSystem - vaccination status-reason

The list of vaccination status reason

CodeSystem - Vaccine Administration Route

The list of administration routes for vaccines

ValueSet - Care location

The list of Care locations

ValueSet - Vaccine Administration Route

The list of administration routes for vaccines

ValueSet - vaccination confirmation status

The list of vaccination confirmation status

ValueSet - vaccination status reason

The list of vaccination status reason

Extension - Administered Product

Administered Product

Extension - Vaccination original order

Vaccination original order (e.g. prescription)

Extension - Vaccination recorder

Vaccination recorder

Extension - Vaccination confirmation status

Vaccination confirmation status

NamingSystem - CNK Code

Naming System - CNK Product Codes

NamingSystem - NIHDI Organization

NamingSystem - NIHDI Organization number

NamingSystem - NIHDI Professional

NamingSystem - NIHDI Professional numbers

NamingSystem - ONE Vaccination Id

NamingSystem for ONE vaccination ID

NamingSystem - Product Manufacturer

NamingSystem - Product Manufacturer

Toto - First hexavalent vaccination

Toto - First hexavalent vaccination

Toto - 2nd hexavalent vaccination

Toto - 2nd hexavalent vaccination

Toto - 3rd hexavalent vaccination

Toto - 3rd hexavalent vaccination

Toto - 4th hexavalent vaccination - skipped (fever)

Toto - 4th hexavalent vaccination - skipped (fever)

Toto - 4th hexavalent vaccination

Toto - 4th hexavalent vaccination

Juan - 1st hexa (reported)

Juan - 1st hexa (reported)

Juan - 2nd hexa (hospital)

Juan - 2nd hexa (hospital)

Juan - 3rd hexa (not done)

Juan - 3rd hexa (not done)

Juan - 3rd hexa (effective)

Juan - 3rd hexa (effective)

Eva - HPV 1st dose

Eva - HPV 1st dose

Eva - HPV 2nd dose

Eva - HPV 2nd dose

Julia - refuse HPV

Julia - refuse HPV

Gabriel - Flu vaccine prescription

Gabriel - flu vacccine prescription

Simon - HPV vaccine prescription

Simon - HPV vacccine prescription

Toto reaction - erythema

Toto - example of reaction (erythema)

Toto finding - fever

Toto - example of finding that prevents vaccination (fever)

Simon HPV - work

Simon HPV - work

Aymeric - rotavirus prescription

Aymeric - rotavirus prescription

Aymeric - rotavirus 1st dose

Aymeric - rotavirus 1st dose

Aymeric - rotavirus 2nd dose

Aymeric - rotavirus 2nd dose

Aymeric - rotavirus 3rd dose

Aymeric - rotavirus 3rd dose

Gabriel - influenza vaccine

Gabriel - influenza vaccine

Observation - swelling reaction

Observation - swelling reaction

Problem

The Problem resources are intended to capture a short description of a patient’s clinical condition. The Logical Data Model defines the functional data needs. The vocabulary resources help ensure conformity and data consistency. The profile and extensions define the technical specifications. A set of examples demonstrates the use of the profile.

Logical Model Problem

Problem logical model

Problem core BE profile

The Core BE profile for Problem

Laterality extension

Laterality

Extension - Problem origin type

Extension for Problem origin type

ValueSet - Problem origin type

Set of values for problem origin type

CodeSystem - Problem origin type

Codes for Problem origin type

Code System Problem Category

Code System Problem Category

Value Set Problem Category

Value Set Problem Category

Problem Codes Value Set

Problem Code Value Set

Value Set Laterality

Value Set Laterality

Code System Body Site

Code System Body Site

Value Set Body Site

Value Set Body Site

Score Results

The Score Results resource captures an overal assessment score about a health indicator associated with a patient. The vocabulary resources help ensure conformity and data consistency. The profile defines the technical specifications. A set of examples demonstrates the use of the profile.

Score Result Logical Model

Score Result Logical Model

Score Result Profile

Score Result Observation profile

Example - FINDRISC score result

FIDNRISC score result example, obtained from a QuestionnaireResponse

Score Result Code system

Score Result codes

Score Result Category Code system

Score Result Category

Score Result Value Set

Score Result value set

Score Category Value Set

Score Category value set

Referral Prescription

The Referral Prescription defines the exchange when ordering services such as nursing care, physiotherapy, or diagnostic procedures such as lab, imaging

Logical Model Referral Prescription

Referral Prescription logical model

Structures: Questionnaires

These define forms used by systems conforming to this implementation guide to capture or expose data to end users

FINDRISC Test Questionnaire
Mini Nutritional Assessment Questionnaire
Allergy / Intolerance reporting Questionnaire
Modified Katz scale evaluation Questionnaire
eBirth Questionnaire

Structures: Resource Profiles

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

BePractitionerRole
BePractitioner
StructureDefinition/be-patient

Belgian federal profile for a patient. Initially based on the functional description of the NIHDI. Special remarks for KMEHR users: following elements in KMEHR are not available in this FHIR resource. If needed, an extension can be defined in a future iteration of these specifications: the ‘deathlocation’ (location is not available but the death of the patient is expressed by either date or Boolean cfr. infra.), the ‘insurancystatus’ (covered in a seperate FHIR resource: Coverage), ‘insurancymembership’ (covered in a seperate FHIR resource: Coverage) and ‘profession’ (covered in a possible future FHIR resource: OccupationalData.)

StructureDefinition/be-organization

Belgian federal profile for an organization. Initially based on the functional description of the NIHDI.

BeMEasure

A record of an observation made by the patient or a professional, with or without a measurement device. This is the preferred profile to be used in specified cases like glucose monitoring, BMI, etc. The list of cases that are supported by this profile (and for which this profile is preferred) is evolving, but for those cases that are included, this profile should be used, instead of a generic Observation.

StructureDefinition/be-referralprescription

The common structure for referral prescription.

Structures: Data Type Profiles

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

StructureDefinition/be-address

Belgain federal profile on address, to provide the possibility in the ‘line’ element to provide a seperate streetname, housenumber and postal box. It is always RECOMMENDED to give these elements seperately.

Structures: Extension Definitions

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

StructureDefinition/exposure-risk

Exposure Risk

BeInformParty

Extra parties that need to be informed of the outcome, besides the prescriber.

Terminology: Value Sets

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

ValueSet/be-causativeagent

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

ValueSet/be-reason-referral-status

Codes to explain the current status of a referral prescription.

ValueSet/be-noallergy

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

ValueSet/be-referral-category

Codes to define the high level category for a referral prescription. SNOMED-CT codes in this valueset are just a draft proposal to give a general idea - pending an official valueset.

ValueSet/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.

ValueSet/be-exposureroute

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

Terminology: Code Systems

These define new code systems used by systems conforming to this implementation guide

CodeSystem Mini Nutritional Assessment scale

CodeSystem Mini Nutritional Assessment.

BeStatusReason

Status reason in Belgium. Initially defined as supporting CodeSystem for the referral prescription.

CodeSystem Modified Katz assessment scale

CodeSystem Modified Katz assessment scale for independent living.

Example: Example Instances

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

Example Immunization - immunization-example-childhood-measles
Example Immunization - immunization-example-reaction-swelling
Example Immunization - immunization-example-tetanus-cautious-reinforcement
Example AllergyIntolerance - allergyintolerance-encounterReference
Example Immunization - iex1
Example Immunization - iex3
Example Immunization - immunization-example-1-hpv
Example Immunization - immunization-example-not-given-stock
Example Immunization - immunization-example-prescribed-vaccination
Example Immunization - immunization-example-not-given-contraindication
Example Immunization - covid-jan-1
Example AllergyIntolerance - allergyintolerance-encounterReference-contained
Example Immunization - covid-jan-3
Example Immunization - covid-jan-2-discarded
Example Immunization - immunization-example-mistaken-entry-update
Example Immunization - iex2
Example Immunization - immunization-example-not-given-refusal
Example Immunization - immunization-example-mistaken-entry

Other

These are resources that are used within this implementation guide that do not fit into one of the other categories

Organization/org-kind-en-gezin
Organization/org-sanofi
Encounter/example-encounter-uzgent-contained
Organization/org-msd-belgium
Organization/org-one-brussels
Organization/org-uz-gent
Encounter/example-encounter-uzgent