Belgian MyCareNet Profiles
2.0.0 - STU Belgium flag

This page is part of the HL7 Belgium FHIR Implementation Guide - MyCareNet profiles (v2.0.0: Trial Use) based on FHIR R4. This is the current published version in its permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions

Artifacts Summary

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

Structures: Resource Profiles

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

MyCareNet eAgreement Demand Bundle BE profile

The profile for the demand for an agreement.

MyCareNet eAgreement Claim BE profile

Claim profile for use in the different eAgreement flow from MyCareNet.

MyCareNet eAgreement Claim Response BE profile

Claimresponse profile for use in the different eAgreement flows from MyCareNet.

MyCareNet eAgreement Consult Reply Bundle BE profile

Profile for the reply to consulting eAgreement request in the MyCareNet flows.

MyCareNet eAgreement Demand Reply Bundle BE profile

The profile for the reply on a demand for an agreement in the MyCareNet flows.

MyCareNet eAgreement ServiceRequest BE profile

The ServiceRequest profile for use in the different eAgreement flows from MyCareNet.

MyCareNet eAgreement Service Request Binary BE profile

A supporting profile on Binary for use in the ServiceRequest eAgreement profile from MyCareNet.

MyCareNet eAgreement Consult Bundle BE profile

Profile for the consulting of eAgreement in the MyCareNet flows.

MyCareNet MessageHeader BE profile

This is the generic MessageHeader profile for use in the different eAgreement flows from MyCareNet.

MyCareNet operation outcome BE profile

OperationOutcome profile for the specific error codes of MyCareNet.

MyCareNet eAgreement Claim Kine BE profile

Claim profile for use in the different eAgreement flow from MyCareNet for kine. This profile is a diff on the general be-eagreementclaim.

Terminology: Value Sets

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

ValueSet adjudication reason

Codes for use to describe eAgreement adjudication reasons in the MyCareNet eAgreement flows.

ValueSet message

Codes for use to describe eAgreement messages in the MyCareNet eAgreement flows.

ValueSet product or service

NIHDI codes for use to describe eAgreement products or services in the MyCareNet eAgreement flows.

Terminology: Code Systems

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

CodeSystem agreement errors

Errors in the agreement flows of MyCareNet. These values were delivered by the NIC(Nationaal Intermutualistisch College)/CIN(Collège Intermutualiste National.) Not all codes are defined here, a full list can be found on mycarenet.be.

CodeSystem agreement types

Agreement types for MyCareNet flows. Not all codes are defined here, a full list can be found on mycarenet.be

CodeSystem annex types

Annex types for MyCareNet flows. Not all codes are defined here, a full list can be found on mycarenet.be

CodeSystem decision values

Decision values in the agreement flows of MyCareNet. These values were delivered by the NIC(Nationaal Intermutualistisch College)/CIN(Collège Intermutualiste National.) The codes are not defined here, a full list can be found on mycarenet.be.

CodeSystem message events

Message events for MyCareNet flows.Not all codes are defined here, a full list can be found on mycarenet.be

CodeSystem refusal values

Refusal values in the agreement flows of MyCareNet. These values were delivered by the NIC(Nationaal Intermutualistisch College)/CIN(Collège Intermutualiste National.)

CodeSystem waiting for information values

Waiting for information values in the agreement flows of MyCareNet. These values were delivered by the NIC(Nationaal Intermutualistisch College)/CIN(Collège Intermutualiste National.)

CodeSystem NIHDIPhysiotherapyPathology

Legal pathology situation codes as defined by NIHDI to be used in the pathology registration flows of MyCareNet. These values are managed by NIHDI. The codes are not defined here. Consult the cookbooks on mycarenet.be for concrete usage instructions.

Example: Example Instances

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

ex01

Ask for a new agreement by an hospital with patient identified by national registration number

ex02

Ask for a new agreement by a physiotherapist with patient identified by mutuality registration number

ex03

Ask for a new agreement by a physiotherapist with patient identified by national registration number

ex04

Reply to an ask with an agreement response

ex05

Reply to an ask with an intreatment response

ex06

Reply to an ask with a refusal response

ex07

Reject the ask with a reject response

ex08

Ask for a cancel of an agreement by a physiotherapist

ex09

Ask for a cancel of an agreement by a physiotherapist

ex10

Ask for an extension of an existing agreement by a physiotherapist

ex11

Argue an existing demand by a physiotherapist

ex12

Consult the current demands & agreements by physiotherapist

ex13

Reply to a consult

ex14

Complete an existing agreement by a physiotherapist

ex15

Reply to a complete