This wiki has undergone a migration to Confluence found Here
Difference between revisions of "201601 FHIR Terminology Services"
Jump to navigation
Jump to search
(Created page with "{{subst::Template for FHIR Connectathon Track Proposals}}") |
(Initial content added) |
||
| Line 2: | Line 2: | ||
[[Category:201601_FHIR_Connectathon_Track_Proposals|Jan 2016 Proposals]] | [[Category:201601_FHIR_Connectathon_Track_Proposals|Jan 2016 Proposals]] | ||
__NOTOC__ | __NOTOC__ | ||
| − | = | + | =FHIR Terminology Services= |
==Submitting WG/Project/Implementer Group== | ==Submitting WG/Project/Implementer Group== | ||
<!-- Who is asking for this track? --> | <!-- Who is asking for this track? --> | ||
| + | FHIR Management Group (FMG) | ||
==Justification== | ==Justification== | ||
<!--Why is this an important track to include in the connectathon - include implementer need, impact on ballot, FMM readiness of the resources, etc. --> | <!--Why is this an important track to include in the connectathon - include implementer need, impact on ballot, FMM readiness of the resources, etc. --> | ||
| + | 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. | ||
==Proposed Track Lead== | ==Proposed Track Lead== | ||
<!-- Name, email and Skype id of individual who will coordinate the track at the connectathon --> | <!-- Name, email and Skype id of individual who will coordinate the track at the connectathon --> | ||
| + | Coordinator: [mailto:rrhausam@gmail.com Rob Hausam] (There is a dedicated skype chat for terminology services - Contact Rob to be included - skype id rhausam) | ||
==Expected participants== | ==Expected participants== | ||
| Line 18: | Line 21: | ||
==Roles== | ==Roles== | ||
<!-- Roles are sets of functionality (generally defined by a Conformance resource) that a single system can take on --> | <!-- Roles are sets of functionality (generally defined by a Conformance resource) that a single system can take on --> | ||
| − | === | + | ===FHIR Terminology Server=== |
<!-- Provide a description of the capabilities this role will have within the connectathon --> | <!-- Provide a description of the capabilities this role will have within the connectathon --> | ||
| + | For service providers, implement the following operations from http://hl7.org/fhir/terminology-service.html: | ||
| + | * $expand | ||
| + | * $validate-code (note: there's a set of typos on the terminology service page where this operation is called "validate" but its actually "validate-code" - editorial oversight) | ||
| + | * $lookup | ||
| + | * $translate (note: there's a typo on the terminology service page where the example has '$validate' not '$translate') | ||
| + | |||
| + | 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=== | ||
| + | <!-- Provide a description of the capabilities this role will have within the connectathon --> | ||
| + | Any one 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== | ==Scenarios== | ||
Revision as of 18:52, 17 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.
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
Roles
FHIR Terminology Server
For service providers, implement the following operations from http://hl7.org/fhir/terminology-service.html:
- $expand
- $validate-code (note: there's a set of typos on the terminology service page where this operation is called "validate" but its actually "validate-code" - editorial oversight)
- $lookup
- $translate (note: there's a typo on the terminology service page where the example has '$validate' not '$translate')
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
Any one 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:
