Walk through:

(1)

Walk through:

zulip-posts

v. Irene Zuschlag

Q & A workshop den 26. nov. 2020

Hvis du har brug for at læse dette dokument i et keyboard eller skærmlæservenligt format, så klik venligst på denne knap.

(2)

Will MedCom provide a overview of the

different encounter states, like the hospital notification profile?

• No, the CareCommunication has not different possible Encounter states like the the hospital notification

(3)

(4)

(5)

Will there be test protocols to be used at the certification?

• Yes, but we do not yet know how much will be tested by the

TouchStone server and how much test that will be done manually.

• We are aiming at a testsetup where as much test as possible is carried out in the TouchStone environment, but some test will always be

carried out manually.

(6)

Is it a requirement that we can reply to a

previously received MedCom message with a CareCommunication - which types of MedCom messages should we be able to reply from with a CareCommunication?

• For now, yes the CareCommunication will replace the (X)DIS91

Clinicical Email MedCom message. Basically every MedCom message may be replied with a CareCommunication, but only for now.

• When the FHIR profiles replaces the EDI/OIOXML standards we expect that the use of CareCommunication will be reduced as the FHIR messaging indroduces possibilities for replies within each profile.

• We will add a Use Case with this scenario and update the documentation

(7)

Is the external classification service for categories and types of attachments mandatory to use? And what if you allow a new attachment type that a

receiving system do not support?

• The classification server is not mandatory to use

• The CareCommunication categories are mandatory to use

• Only the limited types of attachment is allowed – the MedCom test and certification session will contain tests that validate that all types are correctly received and made visible for the end user. If a new type of attachment is added a new MedCom certification is required

(8)

As we have to support a transition period - how do we know what to send, a CareCommunication or a ClinicalEmail?

What is the expectation to the length of the transition period?

• The transistion period is not settled yet, and neither the period

(9)

(10)

How will MedCom test the FHIR implantations?

FHIR test strategy

(11)

Testprotocol –bested on use cases

26-11-2020 11

• VANSEnvelope

• FHIR profiles

• FHIR OperationOutcome

(12)

Touchstone Test

26-11-2020 12

• API testtool

• Clear requirements

• Easier self testing and

documentation of own testing.

(13)

Touchstone Test Suits

26-11-2020 13

(14)

Touchstone error messages and feedback

26-11-2020 14

(15)

FHIR resource instance validation

26-11-2020 15

How to validate a MedCom FHIR resource instance in XML or JSON against the MedCom FHIR IG-Implementation Guide

(16)

FHIR resource instance validation -local

26-11-2020 16

Preconditions

-Download the FHIR validator:

https://confluence.hl7.org/pages/viewpage.action?pageId=35718580#UsingtheF HIRValidator-Downloadingthevalidator

-XML or JSON file with the FHIR recourse instance for testing.

-Java is required

Example of validation

The following example can be used in a CLI If the .XML or .JSON file is stored in the same directory as the FHIR validator

java -jar validator_cli Patient-example.xml -version 4.0 -ig http://build.fhir.org/ig/hl7dk/dk-medcom

For further information regarding the validator: https://confluence.hl7.org/display/FHIR/Using+the+FHIR+Validator

(17)

FHIR resource instance validation - Server

26-11-2020 17

MedCom FHIR test server based on the HAPI FHIR implementation. The test server can be accessed at http://fhir.medcom.dk/

Preconditions

http post client is required

FHIR recourse instant is required Example of validation

The following example is validating a medcom-messaging-messageHeader with Postman [PM] against the MedCom FHIR testserver.

Url: http://

http://fhir.medcom.dk/fhir/Bundle/$validate?profile=http://medcom.dk/fhir/me dcom-core/StructureDefinition/medcom-messaging-messageHeader

(18)

FHIR resource instance validation - Server

26-11-2020 18

(19)

November 26. 2020

FHIR messaging

• Publication v. 1.0

• Test and Certification

(20)

Plans for release 1.0

• Q&A upon release version 0.9 by October 26. November 26., 2020

• Clarification of Documentation version 0.9

• Workshop #4 January

11., 2021

• Dokumentation version 1.0 release-candidate

• Presentation of the Testscripts

• Demo of Touchstone Testtool

• Release version 1.0 Week 4, 2021

• Approval by the National Authority (RUSA)

• Publication

• Test & Certification Before

summer holidays

(21)

Test and Certification

• Touchstone Testtools

• Selftest, until Test Report is free from Errors

• Free Licens allows 5 daily Testruns

• Test and Certification as usual

• Application for Certification

• Appointment for Test Date

• Test between Vendor and MedCom

• Certification granted (on succes)

• Implementation

• Implementation at Health Organizations

• Update SOR with new Capabilities

(22)

Wrap-up of this Q&A session

• Notification have ID for LPR3 and Encounter

• Consistency in Clinical Documentation, use-cases and FHIR profile

regarding Reason for Forwarding

• CareCommunication needs support for reference to other ID than LPR3

• Keep breakable changes at minimum

• Transition strategy soon (reward first-movers)

• Thanks for participation

• Valuable feed-back

Corona Vaccine FHIR-messages Testautomation

Ferrari 488 spider