- Code translation. Often you will have codes in a one code system that need to be translated into codes from another code system. This technique allows you to look up the translation. I've used this to translate local codes to codes from standard vocabularies for:
- Unit translation from ANSI+ to UCUM
- Local codes for problem severity to SNOMED codes for severity used in the HITSP C32
- Local codes for problem status to SNOMED codes for problem status.
- Local codes for problem type to SNOMED codes for problem type.
- Local codes for vital signs to LOINC codes for vital signs.
- Display name lookup. Closely related to #1 above. Often times, I have a standard code, but not the display name associated with it. I can use this technique on small value sets (less that 1000 codes) to look up the display name (this is the use case for the problem presented on the list).
- Mapping from an identifier to a web service end point. You can use this technique to map from:
- The home community ID to an XCA Web Service address
- A DICOM AE Title to a WADO Web Service endpoint.
- Validating against a dynamically changing rule, such as the validation of a code element against the current version of a vocabulary or value set.
<xsl:variable name="myDocument" select="document('mydocument.xml')"/>
This creates a variable which can be used in an XPath expression subsequently in your XML. In the use case the querant posed, the issue was how to get a display name for a language code, to that the patients preferred language (expressed as a code) could be displayed in the UI. The patient's language preferences are stored in the patient/languageCommunication/languageCode/@code attribute.
The following XSLT fragment shows a template that will return the display name of the patient language by looking it up through an XML document.
<xsl:variable name="langs" select="document('lang.xml')"/>
<!-- get the code -->
<xsl:variable name='mappedLang' select='$langs//language[@code=$lang]'/>
The same technique can also be used to access a resource that is created dynamically through a RESTful web-server end-point. I demonstrate one use of this technique in the post on Values Sets and Query Health.
Another use for this technique is to check value-set conformance inside Schematron rules. If you have a requirement that code/@code come from a particular value set, you can write a rule that accesses a web resource based on the value set, as in the following example:
<rule context='*/cda:templateId[@root = templateIdentifier]'>
<let name='code' value='cda:code/@code'/>
<let name='valueSetDoc' value='document("https://example.com/RetrieveValueSet?id=1.2.840.10008.6.1.308")'/>
<assert test='$valueSetDoc//ihe:Concept[@code = $code]'>
The code/@code element must come from the XXX Value Set (OID: 1.2.840.10008.6.1.308)
The use of external XML data files is a very powerful feature of XSLT. Combining that use with dynamically created XML resources through web services makes it even more capable.