FAQ
Can I still browse, search, and download terminology content in various formats as needed (e.g., RF2, JSON/XML, Excel)?
Yes, our Terminology Server allows you to seamlessly browse, search, and download terminology content in multiple formats to fit your needs. Through FHIR APIs, you can integrate terminology content programmatically and access files in FHIR-compliant XML and JSON formats, as well as simplified CSV representations for operations like ValueSet $expand. You can automate the downloads for terminology resources using the Syndication API feed, which provides detailed listings for each CodeSystem. Additionally, the Shrimp Browser provides an intuitive way to search and explore terminology content, while our enhanced OntoCommand interface enables direct downloads of CodeSystems and ValueSet artifacts in your preferred formats.
Can the Terminology Server support the ValueSet compose element to perform the $validate-code operation?
Yes, the Terminology Server is designed to support all FHIR terminology operations including the ValueSets compose element (both intensional and extensional) to perform the $validate-code operation. ValueSets are loaded as composed on the Terminology Server. This enables enhanced functionality, including $validate-code, and allows for $expand operations. The $expand operation supports full expansion requests and a wide variety of parameterized and focused expansions. For more information, please refer to the HL7 FHIR documentation.
I'm having trouble logging in. What should I do?
If you encounter issues logging in, please follow these steps:
1. Refresh the page: Sometimes a simple refresh can resolve the issue.
2. Clear your browser cookies: This can help eliminate any cached data that might be causing the problem.
3. Try a different browser: Access the site using a different web browser to see if the issue persists.
If you've tried all these steps and are still experiencing problems, please contact us for further assistance.
Is the expectation that consumer systems can have runtime use of the Terminology Server?
Yes, the expectation is that the consumer systems can have runtime use of the terminology Server.
Does the Terminology Server need to integrate with systems such as EHR or CIS systems to work, or can it function as a standalone solution?
The Terminology Server is designed to be flexible and can function both as an integrated component and as a standalone solution. With the FHIR APIs, the Terminology Server can support vendor-specific functions, allowing systems to find specific representations of terminology as needed.
When viewing all available versions of a Code System, does “latest” refer to the most recent version that is available in the Shrimp browser?
Yes, “latest” refers to the most recent version of the Code System available in the current versioning stream. We aim to ensure that the most up-to-date content is accessible in the Terminology Server.
Does the solution support integration with local systems? For example, can I use an API to download and insert code set content into a separate database and does the same functionality exist for all Code Systems such as SNOMED CT IE and LOINC on the Syndication server?
Yes, there are two ways to access this content. One method involves using an API, such as Postman, which can handle larger datasets without the limitations that may be encountered with other tools. If you need access to the entire content, the Syndication server allows you to retrieve the full artifact. Depending on your needs, it’s important to choose the correct format for downloading the content. We always make the FHIR representation available, with the exception of SNOMED CT and LOINC. For these two Code Systems, there are binary and native versions, as they cannot be represented in a flat Code System. For simpler, standard artifacts, the Syndication system provides all the necessary data.
From the FHIR perspective, the national SNOMED CT IE Edition code system is the default global code system. Use of “version’ would be included to denote that a code is from the Irish Edition.