Difference between revisions of "Sharing Valuesets, Codes and Maps (SVCM)"
m (→Specification) |
|||
(2 intermediate revisions by 2 users not shown) | |||
Line 37: | Line 37: | ||
==Specification== | ==Specification== | ||
− | '''Profile Status:''' [[ | + | '''Profile Status:''' [[Comments| Trial Implementation]] |
'''Documents:''' | '''Documents:''' | ||
− | * [https://www.ihe.net/uploadedFiles/Documents/ITI/ | + | * [https://www.ihe.net/uploadedFiles/Documents/ITI/IHE_ITI_Suppl_SVCM.pdf Sharing Valuesets, Codes, and Maps (SVCM)] |
'''Additional Supplements:''' | '''Additional Supplements:''' | ||
* [http://www.ihe.net/uploadedFiles/Documents/ITI/IHE_ITI_Suppl_Appx-Z.pdf Appendix Z on HL7 FHIR] | * [http://www.ihe.net/uploadedFiles/Documents/ITI/IHE_ITI_Suppl_Appx-Z.pdf Appendix Z on HL7 FHIR] | ||
Line 68: | Line 68: | ||
|} | |} | ||
+ | '''Open Source''' | ||
+ | * XML transforms for [[SVS]] to/from SVCM -- https://github.com/AudaciousInquiry/svstofhir | ||
Revision as of 14:06, 29 May 2020
The Sharing Valuesets, Codes, and Maps (SVCM) Profile defines a lightweight interface through which healthcare systems may retrieve centrally managed uniform nomenclature and mappings between code systems based on the HL7 Fast Healthcare Interoperability Resources (FHIR) specification
Summary
The Sharing Valusets, Codes, and Maps (SVCM) Profile supports querying for value sets and code systems using the standard HL7 FHIR resources. It also supports looking up and validating codes as well as expanding a value set to list all the available codes. Optionally concept maps can also be included to translate from one code system or value set to another (e.g. SNOMED CT to LOINC).
Benefits
Terminologies managed in value sets are most useful when they are widely shared and standardized across geography and disciplines to add clarity and specificity.
Details
The Sharing Valusets, Codes, and Maps (SVCM) Profile defines a Terminology Repository that can respond to queries from a Terminology Consumer. The consumer can search for HL7 FHIR ValueSets, CodeSystems, and optionally ConceptMaps or retrieve the details if the id is already known.
The Terminology Consumer can lookup a code from a ValueSet or CodeSystem to retrieve the details. It can also validate a code to make sure it exists in the ValueSet or CodeSystem.
The Terminology Consumer can expand a ValueSet to retrieve the full list of available codes.
Optionally, a Terminology Consumer can translate codes from one ValueSet to another or from one CodeSystem to another.
Systems Affected
- A system needing to display a list of options from a value set can query the details from a repository..
- A system containing terminology details can respond to lookup and validation queries.
Actors & Transactions:
Specification
Profile Status: Trial Implementation
Documents:
Additional Supplements:
Underlying Standards:
- FHIR
- ValueSet
- CodeSystem
- ConceptMap
See Also
Related Profiles
- Sharing Value Sets [SVS] distributes centrally-managed, common, uniform nomenclatures.
Implementer Information
This supplement uses FHIR R4 defined resources -- ValueSet N, CodeSystem N, and ConceptMap 3. FHIR Maturity Level (FMM) 3-N. |
Open Source
- XML transforms for SVS to/from SVCM -- https://github.com/AudaciousInquiry/svstofhir
This page is based on the Profile Overview Template