Extensions for Using Data Elements from FHIR R5 in FHIR R4 - Downloaded Version null See the Directory of published versions
| Page standards status: Trial-use | Maturity Level: 0 |
{
"resourceType" : "CodeSystem",
"id" : "usage-context-agreement-scope",
"text" : {
"status" : "generated",
"div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n <p>This code system \n <code>http://hl7.org/fhir/CodeSystem/usage-context-agreement-scope</code> defines the following codes:\n </p>\n <table class=\"codes\">\n <tr>\n <td style=\"white-space:nowrap\">\n <b>Code</b>\n </td>\n <td>\n <b>Display</b>\n </td>\n <td>\n <b>Definition</b>\n </td>\n </tr>\n <tr>\n <td style=\"white-space:nowrap\">realm-base\n <a name=\"usage-context-agreement-scope-realm-base\"> </a>\n </td>\n <td>Realm Base</td>\n <td>Defines use-case independent foundational expectations for exchange within a particular country or jurisdiction. Should be accompanied by a jurisdiction. Commonly used as a 'base' for more restrictive artifacts.</td>\n </tr>\n <tr>\n <td style=\"white-space:nowrap\">knowledge\n <a name=\"usage-context-agreement-scope-knowledge\"> </a>\n </td>\n <td>Knowledge</td>\n <td>Defines use-case-specific information or guidance that is relevant to a specific business or health domain but is not mandated for particular use.</td>\n </tr>\n <tr>\n <td style=\"white-space:nowrap\">domain\n <a name=\"usage-context-agreement-scope-domain\"> </a>\n </td>\n <td>Domain</td>\n <td>Defines use-case-specific requirements for a specific business or health domain. May vary in jurisdictional scope from international to small region and in business scope from broad to narrow.</td>\n </tr>\n <tr>\n <td style=\"white-space:nowrap\">community\n <a name=\"usage-context-agreement-scope-community\"> </a>\n </td>\n <td>Community</td>\n <td>Sets contractual or business expectations for systems participating in a particular exchange community.</td>\n </tr>\n <tr>\n <td style=\"white-space:nowrap\">system-design\n <a name=\"usage-context-agreement-scope-system-design\"> </a>\n </td>\n <td>System Design</td>\n <td>Documents the specific capabilities of a single system as 'available' for purchase or use. May have some variability reflecting options that can be configured.</td>\n </tr>\n <tr>\n <td style=\"white-space:nowrap\">system-implementation\n <a name=\"usage-context-agreement-scope-system-implementation\"> </a>\n </td>\n <td>System Implementation</td>\n <td>Documents the specific points of a single production system or endpoint. This may be time-specific - i.e. reflecting the system 'as it is now' or 'as it was at some point in the past'.</td>\n </tr>\n </table>\n </div>"
},
"extension" : [
{
"extension" : [
{
"url" : "packageId",
"valueId" : "hl7.fhir.uv.xver-r5.r4"
},
{
"url" : "version",
"valueString" : "0.1.0"
},
{
"url" : "uri",
"valueUri" : "http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r5.r4"
}
],
"url" : "http://hl7.org/fhir/StructureDefinition/package-source"
},
{
"url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg",
"valueCode" : "fhir"
}
],
"url" : "http://hl7.org/fhir/CodeSystem/usage-context-agreement-scope",
"version" : "5.0.0",
"name" : "UsageContextAgreementScope",
"title" : "Usage Context Agreement Scope",
"status" : "draft",
"experimental" : false,
"date" : "2026-03-20T15:40:41+11:00",
"publisher" : "FHIR Infrastructure",
"contact" : [
{
"name" : "FHIR Infrastructure",
"telecom" : [
{
"system" : "url",
"value" : "http://www.hl7.org/Special/committees/fiwg"
}
]
}
],
"description" : "This codesystem defines codes describing the type of agreement represented by an artifact, for example for use in CanonicalResource.usageContext.",
"jurisdiction" : [
{
"coding" : [
{
"system" : "http://unstats.un.org/unsd/methods/m49/m49.htm",
"code" : "001",
"display" : "World"
}
]
}
],
"caseSensitive" : true,
"valueSet" : "http://hl7.org/fhir/ValueSet/usage-context-agreement-scope",
"content" : "complete",
"concept" : [
{
"code" : "realm-base",
"display" : "Realm Base",
"definition" : "Defines use-case independent foundational expectations for exchange within a particular country or jurisdiction. Should be accompanied by a jurisdiction. Commonly used as a 'base' for more restrictive artifacts."
},
{
"code" : "knowledge",
"display" : "Knowledge",
"definition" : "Defines use-case-specific information or guidance that is relevant to a specific business or health domain but is not mandated for particular use."
},
{
"code" : "domain",
"display" : "Domain",
"definition" : "Defines use-case-specific requirements for a specific business or health domain. May vary in jurisdictional scope from international to small region and in business scope from broad to narrow."
},
{
"code" : "community",
"display" : "Community",
"definition" : "Sets contractual or business expectations for systems participating in a particular exchange community."
},
{
"code" : "system-design",
"display" : "System Design",
"definition" : "Documents the specific capabilities of a single system as 'available' for purchase or use. May have some variability reflecting options that can be configured."
},
{
"code" : "system-implementation",
"display" : "System Implementation",
"definition" : "Documents the specific points of a single production system or endpoint. This may be time-specific - i.e. reflecting the system 'as it is now' or 'as it was at some point in the past'."
}
]
}