This page is part of the FHIR Specification (v5.0.0: R5 - STU). This is the current published version. For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3 R2
Terminology Infrastructure Work Group | Maturity Level: N/A | Standards Status: Informative | Security Category: Anonymous | Compartments: No defined compartments |
As well as the specific example below, there are many value sets published as part of defining other resources. See:
Example Name | id | Format | |||
ValueSet Example using enumeration of codes (extensional) | example | XML | JSON | Turtle | |
ValueSet Example using code filter (intensional) | example-intensional | XML | JSON | Turtle | |
ValueSet Example using code filter (intensional) defined in a code system resource | example-filter | XML | JSON | Turtle | |
ValueSet Example using a prepared expansion | example-expansion | XML | JSON | Turtle | |
Common UCUM codes | ucum-common | XML | JSON | Turtle | |
All CPT codes | example-cpt-all | XML | JSON | Turtle | |
Yes/No/Don't know, for capturing a common answer set in questionnaires | yesnodontknow | XML | JSON | Turtle | |
NHIN Purpose of Use | nhin-purposeofuse | XML | JSON | Turtle | |
ValueSet including inactive concepts | inactive | XML | JSON | Turtle | |
Example Value Set Metadata | example-metadata | XML | JSON | Turtle | |
Example Value Set Metadata v2 | example-metadata-2 | XML | JSON | Turtle | |
Usage note: every effort has been made to ensure that the examples are correct and useful, but they are not a normative part of the specification.