Belgian MyCareNet Profiles, published by eHealth Platform. This guide is not an authorized publication; it is the continuous build for version 2.2.1 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/hl7-be/mycarenet/ and changes regularly. See the Directory of published versions

Home

Official URL: https://www.ehealth.fgov.be/standards/fhir/mycarenet/ImplementationGuide/hl7.fhir.be.mycarenet				Version: 2.2.1	Highlight text changes?
IG Standards status: Trial-use				Maturity Level: 1	Computable Name: MyCareNet
Other Identifiers: OID:2.16.840.1.113883.4.642.40.200.6

This is our FHIR Implementation Guide. It contains the specifications developed by our community.

Content

With this FHIR Implementation Guide eHealth Platform, in collaboration with the MycareNet team, publishes guidelines, specific profiles and underlying valuesets, codesystems etc.

As such, they are the base Belgian MyCareNet profiles and projects can use them, refer to them and build on them in their use cases.

When needed, eHealth Platform does these publications as downloadable technical profiles according to the FHIR specs as published in this Implementation Guide. As a general rule, the FHIR Belgian MyCareNet standard is used as close as possible to the basic HL7 published standard. As a consequence of this, when needed eHealth Platform will only focus on nuances and clarifications between the Belgian MyCareNet initiative and the published standard.

There will be no Belgian federal publications replacing or describing the overall base specifications of the HL7 FHIR standard – the pages by HL7 are considered to be sufficient.

Implementers are encouraged to study the descriptions of the various FHIR resources published by HL7, the published Belgian “MyCareNet“ profiles here and to signal support@be-ehealth-standards.atlassian.net concerning any ambiguities or initiatives that go outside of that realm.

Implementers SHALL take note every instance of a resource SHALL always explicitely mark when a Belgian MyCareNet or other profile has been used. Implementers SHALL be aware resources using different technical profiles might follow different rules.

The Belgian MyCareNet profiling effort consists of an iterative approach.

Other profiles will be created and/or validated and added to this Belgian MyCareNet set on an ongoing use case driven basis.

This specification contains:

• Generalities on this page
• Content specifics on the Guidance page
• Resource Belgian MyCareNet profiles, which constitute the basis for Belgian MyCareNet FHIR profiling and can be reused in other profiles
• Value Sets, containing specific Belgian MyCareNet value sets
• Code Systems, containing specific Belgian MyCareNet code systems
• Examples, note every effort has been made to ensure the examples are correct and useful, but they are not a normative part of the specification.

The implementation guide is structured to allow implementers to pick and choose the capabilities they need and combine them as necessary.

The top menu allows quick navigation to the different sections, and a Table of Contents is provided with the entire content of this Implementation Guide. (Be aware that some pages have multiple tabs).

Version History

A list of changes to the specification since its initial release.

Dependencies

This IG Contains the following dependencies on other IGs.

Package hl7.fhir.uv.extensions.r4#5.4.0 This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Wed, Oct 28, 2026 08:43+1100+11:00)

Package hl7.fhir.uv.extensions.r4#5.1.0 This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Sat, Apr 27, 2024 18:39+1000+10:00)

Package hl7.fhir.be.core#2.1.2 eHealth Platform Federal Core Profiles (built Fri, Aug 30, 2024 17:07+0200+02:00)

Package hl7.fhir.uv.extensions.r4#5.2.0 This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Mon, Feb 10, 2025 21:45+1100+11:00)

Package hl7.fhir.be.nihdi-terminology#1.1.0 Terminology managed by the NIHDI (RIZIV/INAMI) in various publication, such as https://www.inami.fgov.be/SiteCollectionDocuments/instructions_facturation_electronique.pdf (built Thu, Apr 23, 2026 10:27+0200+02:00)

Package hl7.fhir.uv.tools.r4#1.3.0 This IG defines the extensions that the tools use internally. Some of these extensions are content that are being evaluated for elevation into the main spec, and others are tooling concerns (built Tue, Oct 6, 2026 15:55+1100+11:00)

Cross Version Analysis

This is an R4 IG. None of the features it uses are changed in R4B, so it can be used as is with R4B systems. Packages for both R4 (hl7.fhir.be.mycarenet.r4) and R4B (hl7.fhir.be.mycarenet.r4b) are available.

Intellectual Property

This publication includes IP covered under the following statements.

• ISO maintains the copyright on the country codes, and controls its use carefully. For further details see the ISO 3166 web page: https://www.iso.org/iso-3166-country-codes.html
  Show Usage
  • ISO 3166-1 Codes for the representation of names of countries and their subdivisions — Part 1: Country code: BeCMISOToothSnomedCT, BeCSHolderCode1... Show 40 more, BeCSHolderCode2, BeEAgreementAdjudicationReason, BeExtItemPatientFee, BeExtItemReimbursement, BeExtSystem, BeMessageEAgreement, BeModelEAgreement, BeModelEAgreementResponse, BeMyCareNetCoverage, BeMyCareNetEAgreementDemand, BeMyCareNetEagreementClaim, BeMyCareNetEagreementClaimResponse, BeMyCareNetEagreementConsultReply, BeMyCareNetEagreementDemandReply, BeMyCareNetEagreementServiceRequest, BeMyCareNetEagreementServiceRequestBinary, BeMyCareNetEagreementconsult, BeMyCareNetMessageHeader, BeMyCareNetOperationOutcome, BeNSClaimRelatedClaim, BeProductOrServiceNihdiEAgreement, BeVSBasicLaterality, BeVSDecisionValues, BeVSEagreementErrors, BeVSHolderCode1, BeVSHolderCode2, BeVSToothNumberBodySite, MyBeMyCareNetEagreementClaimKine, MyBeMyCareNetEagreementClaimLogo, MyCareNet, MyCareNetAgreementErrors, MyCareNetAgreementTypes, MyCareNetAnnexTypes, MyCareNetDecisionValues, MyCareNetMessageEvents, MyCareNetRefusalValues, MyCareNetWaitingForInformationValues, NIHDIPhysiotherapyPathologySituationCode, preAuthRef and subType
• This material contains content that is copyright of SNOMED International. Implementers of these specifications must have the appropriate SNOMED CT Affiliate license - for more information contact https://www.snomed.org/get-snomed or info@snomed.org.
  Show Usage
  • SNOMED Clinical Terms® (SNOMED CT®): BeVSBasicLaterality, BeVSToothNumberBodySite... Show 9 more, Bundle/ex01, Bundle/ex02, Bundle/ex03, Bundle/ex10, Bundle/ex14, Bundle/ex16, Bundle/ex17, Bundle/ex29 and MyBeMyCareNetEagreementClaimLogo
• This material derives from the HL7 Terminology (THO). THO is copyright ©1989+ Health Level Seven International and is made available under the CC0 designation. For more licensing information see: https://terminology.hl7.org/license.html
  Show Usage
  • Claim Type Codes: Bundle/ex01, Bundle/ex02... Show 25 more, Bundle/ex03, Bundle/ex04, Bundle/ex05, Bundle/ex06, Bundle/ex08, Bundle/ex09, Bundle/ex10, Bundle/ex11, Bundle/ex13, Bundle/ex14, Bundle/ex15, Bundle/ex16, Bundle/ex17, Bundle/ex18, Bundle/ex19, Bundle/ex20, Bundle/ex21, Bundle/ex22, Bundle/ex23, Bundle/ex27, Bundle/ex29, Bundle/ex30, Bundle/ex33, Bundle/ex35 and Bundle/ex36
  • Claim Information Category Codes: Bundle/ex01, Bundle/ex02... Show 7 more, Bundle/ex03, Bundle/ex10, Bundle/ex11, Bundle/ex16, Bundle/ex17, Bundle/ex29 and Bundle/ex33
  • Process Priority Codes: Bundle/ex01, Bundle/ex02... Show 10 more, Bundle/ex03, Bundle/ex08, Bundle/ex10, Bundle/ex11, Bundle/ex14, Bundle/ex16, Bundle/ex17, Bundle/ex22, Bundle/ex29 and Bundle/ex33

Disclaimer

The specification herewith documented is the first published version of the Belgian MyCareNet profiling initiative. Every effort has been made to remain within the FHIR standard and to be enabling in nature above all else. It is expected there will be further clarifications and guidelines in the future. Should an implementation encounter ambiguities due to this guide, your feedback is most welcome on support@be-ehealth-standards.atlassian.net.