qa:Template TO: verschil tussen versies
(→Release notes (Not part of the template): added clarification) |
k |
||
| Regel 173: | Regel 173: | ||
== Release notes (Not part of the template) == | == Release notes (Not part of the template) == | ||
| − | Release notes are not a part of the TO template because this information about the information standard should already be available in the FO [https://nictiznl.sharepoint.com/sites/KHSI/Kwaliteitshandboek%20Standaardisatie/Stappenplan%20patchrelease.aspx]. Moreover, release notes for technical implementation are already published in the | + | Release notes are not a part of the TO template because this information about the information standard should already be available in the FO. This is described in the [https://nictiznl.sharepoint.com/sites/KHSI/Kwaliteitshandboek%20Standaardisatie/Stappenplan%20patchrelease.aspx | Kwaliteitshandboek Standaardisatie - Stappenplan patchrelease]. Moreover, release notes for technical implementation are already published in the [https://simplifier.net/organization/nictiz/~packages | Nictiz Simplifier packages] and [https://github.com/Nictiz | GitHub] pages. |
In onderstaande tabel staan alle wijzigingen met betrekking tot dit Quality Assurance (QA) Proces, vanaf versie 3.0.0. | In onderstaande tabel staan alle wijzigingen met betrekking tot dit Quality Assurance (QA) Proces, vanaf versie 3.0.0. | ||
Versie van 25 jun 2025 om 10:44
 |
This article or section is in the middle of an expansion or major restructuring and is not yet ready for use. |
| Processen: | Verkennen | Ontwikkelen & Testen | Publiceren | Beheren | Kwalificeren |
|---|
1 Guidance
This section provides general disclaimers for the implementation and use of this information standard.
1.1 Support
For questions, feedback, or change requests, please contact the support team at https://nictiz.atlassian.net/servicedesk/customer/portal/4
1.2 Known issues
The information standard described in this document is actively maintained and continuously improved. However, certain limitations may exist due to ongoing development, external dependencies, or the complexity of healthcare interoperability. The known issues listed here are intended to promote transparency and help implementers plan accordingly.
2 Introduction
This is the FHIR implementation guide (IG) for the information standard [informatiestandaard]. This IG must be used together with the functional specification: [[Landingspagina_[informatiestandaard]| see [informatiestandaard] main page]].
In addition, the guidelines as specified in general FHIR STU3 Implementation Guide apply. The guide defines how to implement FHIR STU3 and what rules apply (e.g. how to handle empty reponses etc.). In particular, the reader should take note of the use case overarching principles and the use of FHIR packages.
3 Boundaries & relationships
4 Workflow & transactions
MJ
Beginnen met aankaarten van "speciale workflows" (o.a. Notified Pull), als dit er is verwijzen naar de pagina's die de juiste info bevatten.
Diagrammen aangeven over welke flows doorlopen worden door de specifieke partijen - zoals bijvoorbeeld IHE dat doet in Technische ontwerp
5 Actors involved
6 Use-cases
In dit hoofdstuk wordt vanuit de gekozen techniek (e.g., FHIR) een technische uitwerking gegeven via invocations (e.g., FHIR queries). Een Transactie in ART-DECOR kun je zien als een maximaal bericht (die van toepassing is op meerdere use-cases). Via queries wordt de uitwisseling verder aangescherpt. Via optionele bereik parameters (e.g. lastn) kan voor meerdere use-cases in de gegevensuitwisseling worden voorzien.
FHIR query specificatie kan via een tabel met de volgende kolommen
- . Query (inc gekozen resources)
- . Code parameters
- . Optionele 'bereik' parameters
- . Relevante profielen
- . toelichting
6.1 Example 1
6.1.1 Invocations
6.2 Example 2
6.2.1 Invocations
thema's als NP verdienen een specifiek hoofdstuk. De NP gaat 'horizontaal' door meerdere use cases.
7 Data exchange standard
DP
The contents of this chapter change based on the chosen data exchange standard. Supported are HL7 FHIR, HL7 CDA, and HL7 v2.
Information included in this chapter:
- Artifacts - which artifacts are exchanged (e.g., FHIR profiles)?
- Artifacts - how do the HCIM's link to the artifacts?
7.1 HL7 FHIR
Every implementation of the standard will require the availability of the information presented here.
7.1.1 Artifacts
This section is to show the link between HCIM and FHIR resources. The table should follow the structure of the FO and refer to the FO (e.g., see FO).
For example, the link to the BgZ-MSZ 2.0 FO would be: [2.0 Chapter 2.1.1]
In the BgZ 2.0 FO the data is sectioned off in chapters and sections. Therefore, the table would use the following headers:
- Chapter - The relevant chapter from the FO.
- HCIM - The name of the HCIM to be exchanged.
- Target - The FHIR resource or data element used to exchange the specified HCIM.
- Profile - The FHIR profile used in this information standard. Use Sjabloon Simplifier.
| Chapter | HCIM | Target | Profile |
|---|---|---|---|
| 1 | Patient | Patient | http://nictiz.nl/fhir/StructureDefinition/BgZ-Patient |
| MaritalStatus | Patient.maritalStatus | ||
| 2 | BloodPressure | Observation | http://nictiz.nl/fhir/StructureDefinition/zib-BloodPressure |
| BodyWeight | Observation | http://nictiz.nl/fhir/StructureDefinition/zib-BodyWeight | |
| BodyHeight | Observation | http://nictiz.nl/fhir/StructureDefinition/zib-BodyHeight | |
| 3 | LaboratoryTestResult | Observation | http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation |
| Specimen | http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Specimen | ||
| 4 | Procedure | Procedure | http://nictiz.nl/fhir/StructureDefinition/BgZ-Procedure |
| 5 | Encounter | Encounter | http://nictiz.nl/fhir/StructureDefinition/zib-Encounter |
7.1.2 Examples of FHIR instances
A link to generated FHIR instances in the information standards' Nictiz-testscripts GitHub folder should be included. BgZ-MSZ 2.0 example: Nictiz-testscripts (BgZ-MSZ 2.0)
7.2 HL7 CDA
Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
7.3 HL7 v2
Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
8 References
9 Release notes (Not part of the template)
Release notes are not a part of the TO template because this information about the information standard should already be available in the FO. This is described in the | Kwaliteitshandboek Standaardisatie - Stappenplan patchrelease. Moreover, release notes for technical implementation are already published in the | Nictiz Simplifier packages and | GitHub pages.
In onderstaande tabel staan alle wijzigingen met betrekking tot dit Quality Assurance (QA) Proces, vanaf versie 3.0.0.
| Versie | Datum | Release notes |
|---|---|---|
