cio:V2.0.0 FHIR CiO: verschil tussen versies
(Initial version) |
k |
||
| Regel 1: | Regel 1: | ||
| − | {{Vdraft/InformationBox|This FHIR IG is currently under development and can not be considered stable and ready for use. For questions and change requests regarding this IG, please create a ticket in [{{VersieInfo|BITS|release= | + | {{Vdraft/InformationBox|This FHIR IG is currently under development and can not be considered stable and ready for use. For questions and change requests regarding this IG, please create a ticket in [{{VersieInfo|BITS|release=V2.0.0|namespace=cio}} BITS].}} |
__NUMBEREDHEADINGS__ | __NUMBEREDHEADINGS__ | ||
| Regel 10: | Regel 10: | ||
=Introduction= | =Introduction= | ||
| − | This is the implementation guide for CiO (Dutch: Contra-indicaties en overgevoeligheden, English: Contraindications and intolerances). The functional specification can be found [[cio:Vdraft_Ontwerp_CiO|here]] and is implemented using [https://www.hl7.org/fhir/R4/ HL7 FHIR R4]. This implementation guide assumes that the reader is familiar with both the functional specification and | + | This is the implementation guide (IG) for the information standard CiO (Dutch: Contra-indicaties en overgevoeligheden, English: Contraindications and intolerances), version 2.0.0-beta.1. The functional specification can be found [[cio:Vdraft_Ontwerp_CiO|here]] and is implemented using [https://www.hl7.org/fhir/R4/ HL7 FHIR R4]. This implementation guide assumes that the reader is familiar with both the functional specification and this version of FHIR. |
| − | Apart from this document, the guidelines as specified in the [[FHIR:V1.0_FHIR_IG_R4|general FHIR Implementation Guide]] apply. | + | Apart from this document, the guidelines as specified in the [[FHIR:V1.0_FHIR_IG_R4|general FHIR Implementation Guide]] apply. In particular, the reader should take note of the Overarching principles and the use of FHIR packages. Where the general IG uses the term ‘use case’, this IG follows the functional specification in using the term ‘transaction’ for the various processes that are described. The functional specification uses the term ‘use case’ for more practical examples. |
| + | |||
| + | This IG first describes the boundaries and relationships in place, after which the implementation is described per transaction. | ||
=FHIR profiles= | =FHIR profiles= | ||
Versie van 17 apr 2023 om 16:59
|
|
This FHIR IG is currently under development and can not be considered stable and ready for use. For questions and change requests regarding this IG, please create a ticket in [ BITS]. |
1 Introduction
This is the implementation guide (IG) for the information standard CiO (Dutch: Contra-indicaties en overgevoeligheden, English: Contraindications and intolerances), version 2.0.0-beta.1. The functional specification can be found here and is implemented using HL7 FHIR R4. This implementation guide assumes that the reader is familiar with both the functional specification and this version of FHIR.
Apart from this document, the guidelines as specified in the general FHIR Implementation Guide apply. In particular, the reader should take note of the Overarching principles and the use of FHIR packages. Where the general IG uses the term ‘use case’, this IG follows the functional specification in using the term ‘transaction’ for the various processes that are described. The functional specification uses the term ‘use case’ for more practical examples.
This IG first describes the boundaries and relationships in place, after which the implementation is described per transaction.
2 FHIR profiles
|
|
Nictiz uses the FHIR Packaging mechanism. This conveniently bundles all profiles, terminology, example material and other conformance resources you need into a single archive, which can be downloaded or installed using the appropriate FHIR tooling. This version of the information standard uses the following packages:
Note: packages use Semantic Versioning. Other versions can be used at will as long as they have the same major.minor number or a minor number higher than the stated version. |
3 Release notes
Release notes can be found on the functional design page.
