Richard showed how the test looks when run. Mario said that after Connectathon the testing continues. Frank made the comment that IHE does minimal testing in preparation for a demo, but it’s not full testing. Mario agreed and said that there is no negative testing, so there is a need for testing system to be in the middle to break messages so we can see what happens. Mario says they are working to slowly increase the number of tests at each connectathon so that they will be gradually accepted and used. The other issue is when the resource or standard is not well defined. As tests are written these problems are determined. Ioana makes the comment that the best and first use case for FHIR, at least in the US, seems to be query. So this should be the major focus in testing. But in further discussion the group said that FHIR will be increasingly used as an internal API for EHR systems as they are looking for rest interfaces to connect different parts of their system together. The level of testing and maturity of FHIR is increasing. Now to increase the FHIR Maturity Metric Level (FMM) the resource has to have test cases defined and it has to go to the Connectathon. We can work on creating use cases for immunizations and work on it for the next WGM. Nathan can work with Richard Ettema from Aegis on this. Action: Create a quarter for FHIR Conformance Discussion about how the description of the test cases can be made more generic so that it can be applied to FHIR, V2, V3, etc. Tuesday Q2 Chair: Ioana Scribe: Nathan Bunker Attendees: 7 Quorum: Yes Agenda: Discussion of Strategy for Conformance in FHIR, V3, etc. Discuss strategy to provide input to FHIR on conformance. Discuss generic conformance format that may be applicable to any HL7 product line. A question about how FHIR testing is currently connected to new implementation guides. Richard Ettema is showing this URL: The assertions are currently not very testable. Looking at D.0.3.1. Need to have a tool bag that the tester can use to pick standard options. Now looking at: Looking at scenarios. Drilling down to US Core. Looking at test script for search.
Richard showed how the test looks when run. Mario said that after Connectathon the testing continues. Frank made the comment that IHE does minimal testing in preparation for a demo, but it’s not full testing. Mario agreed and said that there is no negative testing, so there is a need for testing system to be in the middle to break messages so we can see what happens. Mario says they are working to slowly increase the number of tests at each connectathon so that they will be gradually accepted and used. The other issue is when the resource or standard is not well defined. As tests are written these problems are determined. Ioana makes the comment that the best and first use case for FHIR, at least in the US, seems to be query. So this should be the major focus in testing. But in further discussion the group said that FHIR will be increasingly used as an internal API for EHR systems as they are looking for rest interfaces to connect different parts of their system together. The level of testing and maturity of FHIR is increasing. Now to increase the FHIR Maturity Metric Level (FMM) the resource has to have test cases defined and it has to go to the Connectathon. We can work on creating use cases for immunizations and work on it for the next WGM. Nathan can work with Richard Ettema from Aegis on this. Action: Create a quarter for FHIR Conformance Discussion about how the description of the test cases can be made more generic so that it can be applied to FHIR, V2, V3, etc. Tuesday Q2 Chair: Ioana Scribe: Nathan Bunker Attendees: 7 Quorum: Yes Agenda: Discussion of Strategy for Conformance in FHIR, V3, etc. Discuss strategy to provide input to FHIR on conformance. Discuss generic conformance format that may be applicable to any HL7 product line. A question about how FHIR testing is currently connected to new implementation guides. Richard Ettema is showing this URL: The assertions are currently not very testable. Looking at D.0.3.1. Need to have a tool bag that the tester can use to pick standard options. Now looking at: Looking at scenarios. Drilling down to US Core. Looking at test script for search.
HL7%20CGIT%202016%20January%20Minutes%20v01.docx