CareCommunication Test scripts
3.0.0 - release
CareCommunication Test scripts
3.0.0 - release
CareCommunication Test scripts, published by . This guide is not an authorized publication; it is the continuous build for version 3.0.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/medcomdk/dk-medcom-carecommunication-testscripts/ and changes regularly. See the Directory of published versions
| Official URL: http://medcomfhir.dk/ig/carecommunicationtestscripts/ImplementationGuide/medcom.fhir.dk.carecommunicationtestscripts | Version: 3.0.0 | |||
| Active as of 2024-03-08 | Computable Name: CareCommunicationTestscripts | |||
This Implementation Guide (IG) has two purposes: 1) to present test scripts for sending CareCommunication v. 3.0.0, and 2) to present test examples used in the testprotocol for sending and receiving CareCommunication. Both test scripts and test examples are developed by MedCom.
The purpose of the CareCommunication standard is to support digital communication between parties within healthcare, including amongst others the psychiatric and social area. The CareCommunication is used to ensure secure electronic communication of personally identifiable information and is most often used for ad hoc communication.
The following pages contains important information when implementing CareCommunications, as they contain relevant information:
A description of governance concerning change management and versioning of MedComs FHIR artefacts, can be found on here.
Content in this IG can be downloaded under the tab Download. The download includes both test scripts and test examples. It is also possible to download each artifact, on the individual page.
In the Quality Assurance report (QA-report) for this IG there are some errors and warnings. An instance of the errors are: Unable to resolve resource with reference ‘/Fixture/CareCommunication-fixture-new-message.xml and Unable to resolve resource with reference ‘http://medcomfhir.dk/ig/carecommunication/StructureDefinition/medcom-carecommunication-message’. The errors occur when creating a test script, as the fixture and profile are not reachable in the IG. However, they are reachable from TouchStone, why it is of less concern. Vendors who uses the test scripts locally should be aware of the error and e.g. create the fixtures and define the profile locally.
MedCom is responsible for this IG.
If you have any questions, please contact fhir@medcom.dk or write to MedCom’s stream in Zulip.