Difference between revisions of "201601 FHIR Terminology Services"
| Line 18: | Line 18: | ||
==Expected participants== | ==Expected participants== | ||
<!-- List of the individuals and/or organizations that have indicated a desire to attend the connectathon and implement this track --> | <!-- List of the individuals and/or organizations that have indicated a desire to attend the connectathon and implement this track --> | ||
| − | Health Intersections - server | + | *Health Intersections - server |
| − | Aegis - Touchstone tool and test scripts | + | *Aegis - Touchstone tool and test scripts |
| − | Apelon - server | + | *Apelon - server |
| − | Lantana - FHIR services on Trifolia | + | *Lantana - FHIR services on Trifolia |
| − | CSIRO - server | + | *CSIRO - server |
| − | NLM - FHIR services on VSAC | + | *NLM - FHIR services on VSAC |
| − | multiple additional servers | + | *multiple additional servers |
| − | multiple clients | + | *multiple clients |
==Roles== | ==Roles== | ||
Revision as of 04:16, 25 November 2015
FHIR Terminology Services
Submitting WG/Project/Implementer Group
FHIR Management Group (FMG)
Justification
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 set resource, and the underlying code systems. 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.
Proposed Track Lead
Coordinator: Rob Hausam (There is a dedicated skype chat for terminology services - Contact Rob to be included - skype id rhausam)
Expected participants
- Health Intersections - server
- Aegis - Touchstone tool and test scripts
- Apelon - server
- Lantana - FHIR services on Trifolia
- CSIRO - server
- NLM - FHIR services on VSAC
- multiple additional servers
- multiple clients
Roles
FHIR Terminology Server
For service providers, implement the following operations from http://hl7.org/fhir/terminology-service.html:
- $expand - Value Set Expansion
- $validate-code - Value Set Validation
- $lookup - Concept Lookup
- $translate - Translations
- $closure - Maintaining a Closure Table
Service providers are not required to implement all this functionality - it's a lot to do. For new implementers, start at the top and work down (generally)
FHIR Terminology Client Consumer
Implement any one or more of
- do a value set expansion of one of the value sets in the spec
- validate a code using the spec against a FHIR value set, a v2 value set, or LOINC or snomed CT
- look up a display for a code (most appropriate for v2/FHIR conversion)
At least one server supports all these operations (http://fhir2.healthintersections.com.au). Other servers, including the Apelon server (http://fhir.ext.apelon.com:8081/DtsOnFhirDemo) will support some of those operations
Scenarios
Scenario Step 1 Name
- Action:
- Precondition:
- Success Criteria:
- Bonus point:
TestScript(s)
The supporting TestScripts and corresponding fixtures have been committed to the FHIR SVN repository at: http://gforge.hl7.org/svn/fhir/trunk/connectathons/OrlandoJan2016/Connectathon11/Track2-Terminology
TestScript Definitions
The TestScript resources in this folder represent a conversion** of the TestScript originally used at the 1st Terminology Services Connectathon held in Washington, February 2014.
The original single TestScript has been separated into four (4) separate TestScript definitions - one for each original test suite. In addition, each of those TestScripts have two variations based on whether the FHIR client or server assigns the resource id of the required ValueSet resources created in the setup.
**This representation of the Terminology Services tests is not meant to be definitive and complete. This is one example of how these tests can be defined in the current DSTU2 format of the TestScript resource. Constructive feedback, suggestions and criticisms are welcome.
FHIR Resource ID Assigned by the Client
- track2-terminology-ts-suite1-client-id -- Terminology test suite 1 where the FHIR client assigns the ValueSet resource id in the setup.
- track2-terminology-ts-suite2-client-id -- Terminology test suite 2 where the FHIR client assigns the ValueSet resource id in the setup.
- track2-terminology-ts-suite3-client-id -- Terminology test suite 3 where the FHIR client assigns the ValueSet resource id in the setup.
- track2-terminology-ts-suite4-client-id -- Terminology test suite 4 where the FHIR client assigns the ValueSet resource id in the setup.
FHIR Resource ID Assigned by the Server
- track2-terminology-ts-suite1-server-id -- Terminology test suite 1 where the FHIR server assigns the ValueSet resource id in the setup.
- track2-terminology-ts-suite2-server-id -- Terminology test suite 2 where the FHIR server assigns the ValueSet resource id in the setup.
- track2-terminology-ts-suite3-server-id -- Terminology test suite 3 where the FHIR server assigns the ValueSet resource id in the setup.
- track2-terminology-ts-suite4-server-id -- Terminology test suite 4 where the FHIR server assigns the ValueSet resource id in the setup.
Conventions Used
The execution of the TestScript resources contained in this folder are constrained by the following conventions:
Fixtures - All resource reference values can be either url paths or local local file system paths. The convention for these TestScript resources use local file system paths where the execution engine is expected to resolve this path based on the following:
- Leading '/' character - this is resolved as an absolute path based on a known root path.
- No leading '/' character - this is resolved as a relative path based on the location of the TestScript resource file.
