View raw Markdown
type: codesystemcodesystem: usage-context-agreement-scope

Usage Context Agreement Scope

Concepts

CodeDisplayDefinition
realm-baseRealm BaseDefines 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.
knowledgeKnowledgeDefines use-case-specific information or guidance that is relevant to a specific business or health domain but is not mandated for particular use.
domainDomainDefines 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.
communityCommunitySets contractual or business expectations for systems participating in a particular exchange community.
system-designSystem DesignDocuments the specific capabilities of a single system as 'available' for purchase or use. May have some variability reflecting options that can be configured.
system-implementationSystem ImplementationDocuments 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'.

CodeSystem XML

<?xml version="1.0" encoding="UTF-8"?><CodeSystem xmlns="http://hl7.org/fhir">
  <url value="http://hl7.org/fhir/CodeSystem/usage-context-agreement-scope"/>
  <identifier>
    <system value="urn:ietf:rfc:3986"/>
    <value value="urn:oid:2.16.840.1.113883.4.642.4.1798"/>
  </identifier>
  <name value="UsageContextAgreementScope"/>
  <title value="Usage Context Agreement Scope"/>
  <status value="draft"/>
  <experimental value="false"/>
  <description value="This codesystem defines codes describing the type of agreement represented by an artifact, for example for use in CanonicalResource.usageContext."/>
  <caseSensitive value="true"/>
  <content value="complete"/>
  <concept>
    <code value="realm-base"/>
    <display value="Realm Base"/>
    <definition value="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."/>
  </concept>
  <concept>
    <code value="knowledge"/>
    <display value="Knowledge"/>
    <definition value="Defines use-case-specific information or guidance that is relevant to a specific business or health domain but is not mandated for particular use."/>
  </concept>
  <concept>
    <code value="domain"/>
    <display value="Domain"/>
    <definition value="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."/>
  </concept>
  <concept>
    <code value="community"/>
    <display value="Community"/>
    <definition value="Sets contractual or business expectations for systems participating in a particular exchange community."/>
  </concept>
  <concept>
    <code value="system-design"/>
    <display value="System Design"/>
    <definition value="Documents the specific capabilities of a single system as 'available' for purchase or use.  May have some variability reflecting options that can be configured."/>
  </concept>
  <concept>
    <code value="system-implementation"/>
    <display value="System Implementation"/>
    <definition value="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'."/>
  </concept>
</CodeSystem>