2375 résultats

Dear stakeholder/client/developer,...

As a result of all the vaults aligning on the medication scheme element transaction, the specs can now be downloaded on this website. Previously, the specifications were only available with the regional vaults. Further evolutions of this transaction will also be published on the Standards website.

This is the KMEHR table to refer to the legal reference concept (provided by NIHDI) as used in SAM v2. (available in the SAM v2 RMB downloads)
"A legal reference is an “entry point” in the law: a chapter, a paragraph, an article, etc. that can be used to define reimbursement properties. It is defined according to a recursive tree structure with one or more levels. A legal reference has no direct “text content”. The text of a legal reference must be retrieved from the related alinea (“legal text”). The legal text is always linked to the deepest legal reference from the legal references tree." (from the SAM v2 PIM pdf)

The version of the table used is specified in the attribute 'SV' of the cd element: this is an external table, please follow the versioning system proposed by the owner of the table !
This table is used in the Chapter IV flow of MyCareNet. Please refer to the MyCareNet website for examples and further documentation.

This is the KMEHR table to refer to the legal text concept (provided by NIHDI) as used in SAM v2. (available in the SAMv2 RML downloads)
"A legal text is an alinea, which means any text part of the law that has a “textual content”. It is defined according to a recursive tree structure with one or more levels. A legal text may have two parents: a first (mandatory) legal reference parent (which is, for example, the paragraph in which this text is included) and an optional legal text parent (which can be another text that includes the current one). In this way, every legislation text part including a hierarchy with levels containing relevant information for the authentic source can be registered and structured. " (from the SAM v2 PIM pdf)

The version of the table used is specified in the attribute 'SV' of the cd element: this is an external table, please follow the versioning system proposed by the owner of the table !
This table is used in the Chapter IV flow of MyCareNet. Please refer to the MyCareNet website for examples and further documentation.

This is the KMEHR table to refer to the formal interpretation concept (provided by NIHDI) as used in SAM v2. (and available in the SAM v2 RML downloads)
"A legal reference can be modelled in several formal interpretations. A formal interpretation expresses both the Reimbursement conditions and the Reimbursement terms of legal texts. A formal interpretation describes (exactly) one way of gaining “terms” by satisfying a set of conditions." (from the SAM v2 PIM pdf)

The version of the table used is specified in the attribute 'SV' of the cd element: this is an external table, please follow the versioning system proposed by the owner of the table !
This table is used in the Chapter IV flow of MyCareNet. Please refer to the MyCareNet website for examples and further documentation.

This is the KMEHR table to refer to the reimbursement parameter (b, e or d) (provided by NIHDI) as used in SAM v2. (and available in the SAM v2 RML downloads)
"Reimbursement terms are additional information about the result of a reimbursement after approval. For example the validity period of a reimbursement authorization, the maximum quantity that can be reimbursed, …[…]" (From the SAM v2 ReimbLaw Rules and Expressions doc)

The version of the table used is specified in the attribute 'SV' of the cd element: this is an external table, please follow the versioning system proposed by the owner of the table !
This table is used in the Chapter IV flow of MyCareNet. Please refer to the MyCareNet website for examples and further documentation.

This is the KMEHR table to refer to the reimbursement context environment (provided by NIHDI) as used in SAM v2. (and available in the SAM v2 RMB downloads)
"A DMPP can be reimbursement in one or more contexts depending on current legislation. The link with Reimbursement Context is based on Delivery Environment, Code and Code Type only. […]" (from the SAM v2 PIM pdf)

The version of the table used is specified in the attribute 'SV' of the cd element: this is an external table, please follow the versioning system proposed by the owner of the table !
This table is used in the Chapter IV flow of MyCareNet. Please refer to the MyCareNet website for examples and further documentation.

This contents of this table has been defined by NIC/CIN.

Values identify specific transactions for Medical Advisor Agreements.

Context of use: transaction

This contents of this table has been defined by NIC/CIN.

Values identify specific items to be used in the transactions for Medical Advisor Agreements.

Context of use: item

This table is used in the context of the Medical Advisor Agreements (Chapter IV). This contents of this table has been defined by NIC/CIN.

Values identify the coverage types for Medical Advisor Agreements.

Context of use: item

This table is used in the context of the Medical Advisor Agreements (Chapter IV). This contents of this table has been defined by NIC/CIN.

Values identify different refusal justifications for Medical Advisor Agreements.

Context of use: item