- Created by Davera Gabriel, last modified on May 02, 2022
Short Description | Terminology, and the proper use of it, is fundamental for everything that we do in FHIR. The purpose of this track is to test and enhance the capabilities of FHIR Terminology Services and promote their use throughout the FHIR implementation community. |
Long Description | The FHIR specification includes support for the provision of a terminology service - that is, a service that lets healthcare applications make use of codes and value sets without having to become experts in the fine details of the value sets and underlying code systems and their related resources. The management and proper use of terminology is fundamental to effective, interoperable data exchange, so this is an important capability to provide and test in the Connectathons. We expect and hope to achieve: (1) improved capabilities of terminology servers measured by testing performance, (2) improved and more extensive terminology service testing, (3) implementation and implementer experience with aspects of the terminology services specifications, including experience with newer and previously lesser used terminology service operations and operation capabilities, (4) identify potential improvements as well as deficiencies and possibly errors in the FHIR terminology service specifications based on implementation and testing experience, and (5) increased awareness and utilization of terminology services by other Connectathon tracks. |
Type | Test the design of a Resource/set of Resources |
Submitting Work Group/Project/Accelerator/Affiliate/Implementer Group | Terminology Services Management Group |
Track Lead(s) | Davera Gabriel dgabrie4@jhmi.edu |
Track Lead Email(s) | |
Related Tracks | |
FHIR Version | Current build: FHIR R4, R5 |
Specification(s) this track uses | http://hl7.org/fhir/terminology-service.html (R4 Terminology Services) http://build.fhir.org/conceptmap.html (proposed R5 changes to ConceptMap) https://www.hl7.org/fhir/terminologycapabilities.html (Terminology Capabilities) |
Artifacts of focus | http://hl7.org/fhir/terminology-service.html (R4 Terminology Services) http://build.fhir.org/conceptmap.html (proposed R5 changes to ConceptMap) https://www.hl7.org/fhir/terminologycapabilities.html (Terminology Capabilities) |
Expected participants | |
Zulip stream | |
Friday | Friday April 229, 9:30-10:30a EASTERN Join Zoom Meeting Meeting ID: 685 509 3136 Dial by your location Join by Skype for Business In-track Welcome & Kick-off Session: Monday May 2, 11a-noon EASTERN |
Track Details | Breakout Sessions"Ask the Expert" Office HoursAn open, unstructured discussion of HL7 FHIR Terminology current events, resources, and implementation "tips and tricks." Pull up a chair and bring your Connectathon comments, discoveries and unresolved terminology issues to the table. All are welcome. HL7 Vocabulary Office Hours – Rob McClure Tuesday, May 3 & Wednesday, May 4 10-11a (2 sessions) Normative FHIR Terminology Server Capability Statement – Peter Jordan Monday, May 2, 6-7p In addition to bringing his considerable terminology expertise to the session, Peter will be discussing issues pertaining to the normative terminology service capability statement recently surfaced in the Trans-Tasman Connectathon (April29 -30, 2022), including
HL7 Terminology Implementation Issues Office Hours - Reuben Daniels Monday, May 2 & Tuesday May3 5-6 p (2 sessions) Reuben Daniels is a Board Director of the Australian HL7 Affiliate (HL7 Australia), co-chair of the HL7 Vocabulary Working Group, Vice-chair of the HL7 Terminology Authority (HTA), co-chair of the HL7 Terminology Services Management Group (TSMG) and Principal Consultant at Saludax which provides architecture, standards, interoperability, and education consulting services primarily to the Australian digital health sector. Reuben has more than a decade's experience leading standards implementations for software vendors, healthcare organizations, state and federal health departments, and brings his considerable technical knowledge dealing with terminology implementation issues to this session. He has considerable experience in the design, deployment and operation of FHIR-based state and national terminology services. Terminology Servers & Tooling Office Hours - Michael Lawley Monday, May 2 7-8p Dr. Michael Lawley is a Group Leader at the Commonwealth Scientific and Industrial Research Organisation (CSIRO) and leads the Health Informatics Group in the Australian E-Health Research Centre. He is a SNOMED on FHIR co-chair and a member of SNOMED International’s Modelling Advisory Group. In his role with CSIRO, Michael leads the development of technical solutions aiming to address interoperability, terminology and ontological aspects of health research and innovation for Australia, having spent nearly 2 decades prior developing and implementing technology solutions in health research. In this session, Michael will share his significant expertise as a developer of terminology-focused applications, servers, and tools supporting SNOMED CT and FHIR. Additional BreakoutsClinical Genomics Terminology Operations Breakout - Bob Dolin, Bret Heale Tuesday, May 3, 12:30 - 2p The Clinical Genomics WG has developed a new specification that implements code-based searching. In this break-out session, Bob & Bret will review some of the terminology components that are implicit in the FHIR Genomics Operations, such as token vs. codeSystem / code searching and mapping normalization strategies when more than one coding system is permitted by the specification (e.g.: SNOMED CT & Disease Ontology). Clinical Quality Measures Joint Session - Bryn Rhodes Tuesday, May 3, 4-5p (also listed in the Clinical Reasoning Track) Of interest to the Vocabulary community: a joint session with members of the FHIR-based Quality Measures for use in Quality Measurement programs group focused on their use of the Measures Terminology Service and Value Set version validation. Terminology Queries & Representation Syntax - Lloyd McKenzie, Michael Lawley, Josh Mandel, Grahame Grieve Tuesday, May 3 6-7:30p The need to expose a common general hierarchical and filter-based query syntax for use in defining value sets and performing inline queries has come up yet again as evidenced by a recent Zulip chat in the Terminology stream. This session aims to provide a real-time discussion of the topic, and identify the next steps to resolution. Vocabulary Normalization Requirements & Strategies Across HL7 Standards - Lisa Nelson Wednesday, May 4 11a-noon When there is a need to make a move from C-CDA representations to US Core FHIR profile conformant FHIR Resources, a set of best practices is needed where there may not be a need for traditional mapping, as is supported by the ConceptMap resource or other code system-to-code system mappings. In the cases where there is a need to normalize the received information, and possibly add additional codings, what are the rules which will preserve the original information and its provenance, that also add codes which are introduced by an assembler system? Where in the HL7 workflow is this added, and where is the newly added "normalizing" information stored? The purpose of this breakout is to talk through some of the scenarios where the incoming information is C-CDA or V2 and being converted to FHIR resources. R5 Concept Map Review - Rob Hausam Wednesday, May 4, 1-2p In this late-breaking session, Rob Hausam will provide an overview of the FHIR Concept Map resource, with a focus on changes between R4 and R5 System roles:FHIR Terminology ServerFor service providers, implement the following operations from http://hl7.org/fhir/terminology-service.html:
Support additional capabilities:
Service providers are not required to implement all of this functionality - it's a lot to do. For new implementers, start at the top and work down (generally). FHIR Terminology Client ConsumerImplement any one or more of:
At least one server supports all of these operations and capabilities (http://test.fhir.org/r5). Other servers (see the list above) will support several of these operations and capabilities. Scenarios1 - Testing Proposed ConceptMap R5 ChangesFor FHIR R5 significant changes have been made to the ConceptMap resource, including:
Connectathon testing and implementation experience is needed to progress the revised ConceptMap resource through the maturity levels toward normative status. 2 - Formal Testing of Terminology - Participants with FHIR experienceThis scenario introduces a more formalized testing approach for those participants that have been working the FHIR Terminology specification and wish to move beyond basic testing and may have systems that are in active development, deployed or soon to be deployed into a production environment. Automated testing tooling is significantly leveraged for both automated terminology server testing (testing tool to FHIR terminology server) and surveillance of peer-to-peer testing (external FHIR client to external FHIR server). Pre-connectathon testing is highly encouraged in order to be better prepared for the actual Connectathon event and to become familiar with the public testing platforms that will be used for the formal testing. Testing and test reporting will be done using the public testing platforms which will provide test results via the new FHIR TestReport resource type as well as any specific reporting capabilities of those testing platforms. These reports will provide qualitative and quantitative analysis of the system under test and its conformance to the FHIR specification. 3 - NamingSystem $translate-id proposed operation testing (R5)Executing the use of the NamingSystem resource in and with FHIR terminology services and its applications in profiles and IGs, testing the $translate-id operation functionality 4 - Minimum Capabilities for a Terminology ServerA FHIR Terminology Server should be able to support a minimum set of capabilities (behaviors). This activity will provide the opportunity to test whether a terminology server's capability statement is conformant to the minimum set of requirements as established by a vocabulary WG task force described here. As a first step to developing a complete profile and test scenario for minimum Terminology Server capabilities, the $implements on the CapabilityStatement resource is leveraged. Resource testing can be achieved via a POST to https://terminz.azurewebsites.net/fhir/CapabilityStatement/$implements with a CapabilityStatement resource. An OperationOutcome resource with a series of issue elements of varying types will be returned. This server is configured to accommodate the capabilities identified by the task force for a minimum Terminology Server as referenced above. TestScript(s):This track includes formal testing and reporting of test results utilizing a defined set of test scripts. AEGIS Touchstone TestScripts will be available for Connectation 30. Please email Touchstone_Support@aegis.net for any questions about using Touchstone. Available Connectathon 30 Test Script SetsThe test scripts listed below have been updated for Connectathon 30 and scripts for additional tests may be added. Test Scripts - Supported Formats
Test Scripts - ValueSet Expand - $expand
Test Scripts - CodeSystem Lookup - $lookup
Test Scripts - CodeSystem Subsumes - $subsumes
Test Scripts - CodeSystem Translate - $translate
Test Scripts - CodeSystem Validate Code - $validate-code
Test Scripts - ValueSet Validate Code - $validate-code
Test Scripts - NamingSystem Preferred ID - $preferred-id
The AEGIS Touchstone testing tool has test scripts available for tracks to test their implementations. See www.touchstone.com to sign in our register if you are a new user. Below, you will find a link to the tests specific to this HL7 track. Please send questions or issues to touchstone_support@aegis.net and a team member will be glad to assist you. Terminology Tests for Connectathon 30 are found here: Terminology Tests in Touchstone Security and Privacy Considerations:Most FHIR terminology terminology service endpoints are open (at present). This may change in the future as adoption and implementation experience increases in order to more directly manage external (non-HL7) terminology licensing considerations. Some servers do allow or require authentication (e.g. Apelon - see above). |