Page Comparison

Background

The AQL MATCHES statement may perform a request to a terminology server for performing some operation over a value set or code system (here used as a synonym of terminology). Several operations may be possible, being the most common ones: the expansion of a ValueSet, checking that a concept belongs to a value set or code system, testing if one concept subsumes another one, or the translation of concepts across different terminologies.

...

Operation section

The operation section specifies the action to perform over the specified value set or code system. It is not restricted to any particular structure provided that different terminology servers may use different ways of specifying the operation and its parameters. Query implementers should be careful so the specified operation can be properly dereferenced by the implementation of the driver:

• Expand a value set: retrieve all the codes contained in a value set as an explicit set.

• Validate a code in a value set: check if a given code belongs to a value set. Recall that the value set may comprise all the codes in a code system (terminology).

• Look-up a code: retrieve all the information concerning one particular code. Examples are retrieving the preferred form to display, synonyms, etc.

• Translate a code: translate (find an equivalent) code from one Value Set to another one based on a predefined mapping available in the external terminology service. Translation precision may not be limited to full equivalence and different kinds of mappings may be possible (wider meaning, equivalent, narrower meaning, etc).

• Subsumption testing: determine if a particular terminology concept is a subtype (is-a) of another one. For example, test in SNOMED-CT if Myasthenia Gravis | 91637004 is a subtype of autoimmune disease | 85828009 (i.e. test if 85828009 subsumes 91637004).

Operation section

The operation section specifies the action to perform over the specified value set or code system. It is not restricted to any particular structure provided that different terminology servers may use different ways of specifying the operation and its parameters. Query implementers should be careful so the specified operation can be properly dereferenced by the implementation of the driver:

• Expand a value set: retrieve all the codes contained in a value set as an explicit set.

• Validate a code in a value set: check if a given code belongs to a value set. Recall that the value set may comprise all the codes in a code system (terminology).

• Look-up a code: retrieve all the information concerning one particular code. Examples are retrieving the preferred form to display, synonyms, etc.

• Translate a code: translate (find an equivalent) code from one Value Set to another one based on a predefined mapping available in the external terminology service. Translation precision may not be limited to full equivalence and different kinds of mappings may be possible (wider meaning, equivalent, narrower meaning, etc).

• Subsumption testing: determine if a particular terminology concept is a subtype (is-a) of another one. For example, test in SNOMED-CT if Myasthenia Gravis | 91637004 is a subtype of autoimmune disease | 85828009 (i.e. test if 85828009 subsumes 91637004).

...

*Should the grammar restrict the ValueSet section to URI or allow any String so OIDs can fit in the ValueSet specification?

*Which driver format should we use?specification of Concept Maps for translations

Examples

Examples for Validation and Example

...

{{url}}/ValueSet/$validate-code?system=http://loinc.org&code=45276-3&url=http:/loinc.org/vsac/BloodCulture&display=Bacteria identified in Blood by Anaerobe culture 25 degree C incubation

openEHR:

TERMINOLOGY(´http'validate-code', ‘http:/loinc/hl7.org/vsac/BloodCulture´, ´ValueSetfhir/4.0',’ValueSet/$validate-code?system=http://loinc.org&code=45276-3&url=http:/loinc.org/vsac/BloodCulture&display=Bacteria identified in Blood by Anaerobe culture 25 degree C incubation´,´org.hl7.fhir´)incubation'):BOOLEAN

...

EXAMPLE 2

FHIR:

{{url}}/ValueSet/$validate-code?system=http://snomed.info/sct&code=30346009&url=http://vsac.highmed.org/vsac/episodes&display=Evaluation and management of established outpatient in office or other outpatient facility

openEHR: 

TERMINOLOGY( ´‘validate-code', ‘http://vsac.highmedhl7.org/vsac/episodes´, ´ValueSetfhir/4.0', ’ValueSet/$validate-code?system=http://snomed.info/sct&code=30346009&url=http://vsac.highmed.org/vsac/episodes&display=Evaluation´,´org.hl7.fhir´)'):BOOLEAN

...

EXAMPLE 3

FHIR:

{{url}}/ValueSet/$validate-code?system=http://snomed.info/sct&code=122298005&url=http://snomed.info/sct?fhir_vs&display=Astrovirus RNA assay

openEHR: 

TERMINOLOGY(´‘validate-code', ‘http://snomedhl7.info/sct?fhir_vs´,´ValueSetorg/fhir/4.0', ‘ ValueSet/$validate-code?system=http://snomed.info/sct&code=122298005&url=http://snomed.info/sct?fhir_vs&display=Astrovirus RNA assay´ ,´org.hl7.fhir´)assay'):BOOLEAN

...

EXAMPLE 4

FHIR:

{{url}}/ValueSet/$validate-code?system=http://icd10.who.org&url=http://vsac.nlm.nih.gov/malignantneoplasms&code=C15.8&display=foo

openEHR: 

TERMINOLOGY(´http‘validate-code', ‘http://vsac.nlm.nih.gov/malignantneoplasms´, ´ValueSethl7.org/fhir/4.0', ‘ValueSet/$validate-code?system=http://icd10.who.org&url=http://vsac.nlm.nih.gov/malignantneoplasms&code=C15.8&display=foo´,´org.hl7.fhir´)foo’):BOOLEAN

...

EXAMPLE 5

FHIR:

{{url}}/ValueSet/$expand?url=http://snomed.info/sct?fhir_vs=isa/50697003

...