Definition for Code SystemStandardsStatus

<?xml version="1.0" encoding="UTF-8"?>

<CodeSystem xmlns="http://hl7.org/fhir">
  <id value="standards-status"/> 
  <meta> 
    

    <lastUpdated value="2022-09-10T04:52:37.223+10:00"/> 
    <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"/> 
  </meta> 
  <text> 
    <status value="generated"/> 
    <div xmlns="http://www.w3.org/1999/xhtml">
      

      <p> This code system 
        <code> http://hl7.org/fhir/standards-status</code>  defines the following codes:
      </p> 
      <table class="codes">
        <tr> 
          <td style="white-space:nowrap">
            <b> Code</b> 
          </td> 
          <td> 
            <b> Display</b> 
          </td> 
          <td> 
            <b> Definition</b> 
          </td> 
        </tr> 
        <tr> 
          <td style="white-space:nowrap">draft
            <a name="standards-status-draft"> </a> 
          </td> 
          <td> Draft</td> 
          <td> This portion of the specification is not considered to be complete enough or sufficiently
             reviewed to be safe for implementation. It may have known issues or still be in the &quot;in
             development&quot; stage. It is included in the publication as a place-holder, to solicit
             feedback from the implementation community and/or to give implementers some insight as
             to functionality likely to be included in future versions of the specification. Content
             at this level should only be implemented by the brave or desperate and is very much &quot;use
             at your own risk&quot;. The content that is Draft that will usually be elevated to Trial
             Use once review and correction is complete after it has been subjected to ballot.

             reviewed to be safe for implementation. It may have known issues or still be in
             the &quot;in development&quot; stage. It is included in the publication as a place-holder,
             to solicit feedback from the implementation community and/or to give implementers
             some insight as to functionality likely to be included in future versions of the
             specification. Content at this level should only be implemented by the brave or
             desperate and is very much &quot;use at your own risk&quot;. The content that is
             Draft that will usually be elevated to Trial Use once review and correction is
             complete after it has been subjected to ballot.</td> 

        </tr> 
        <tr> 
          <td style="white-space:nowrap">normative
            <a name="standards-status-normative"> </a> 
          </td> 
          <td> Normative</td> 
          This content has been subject to review and production implementation in a wide variety
             of environments. The content is considered to be stable and has been 'locked', subjecting
             it to FHIR Inter-version Compatibility Rules. While changes are possible, they are expected
             to be infrequent and are tightly constrained. Compatibility Rules.

          <td> This content has been subject to review and production implementation in a wide
             variety of environments. The content is considered to be stable and has been 'locked',
             subjecting it to FHIR Inter-version Compatibility Rules. While changes are possible,
             they are expected to be infrequent and are tightly constrained. Compatibility Rules.</td> 

        </tr> 
        <tr> 
          <td style="white-space:nowrap">trial-use
            <a name="standards-status-trial-use"> </a> 
          </td> 
          <td> Trial-Use</td> 
          This content has been well reviewed and is considered by the authors to be ready for use
             in production systems. It has been subjected to ballot and approved as an official standard.
             However, it has not yet seen widespread use in production across the full spectrum of
             environments it is intended to be used in. In some cases, there may be documented known
             issues that require implementation experience to determine appropriate resolutions for.

          <td> This content has been well reviewed and is considered by the authors to be ready
             for use in production systems. It has been subjected to ballot and approved as
             an official standard. However, it has not yet seen widespread use in production
             across the full spectrum of environments it is intended to be used in. In some
             cases, there may be documented known issues that require implementation experience
             to determine appropriate resolutions for.


Future versions of FHIR may make significant changes to Trial Use content that are not
             compatible with previously published content.

Future versions of FHIR may make significant changes to Trial Use content that
             are not compatible with previously published content.</td> 

        </tr> 
        <tr> 
          <td style="white-space:nowrap">informative
            <a name="standards-status-informative"> </a> 
          </td> 
          <td> Informative</td> 
          This portion of the specification is provided for implementer assistance, and does not
             make rules that implementers are required to follow. Typical examples of this content
             in the FHIR specification are tables of contents, registries, examples, and implementer
             advice.

          <td> This portion of the specification is provided for implementer assistance, and does
             not make rules that implementers are required to follow. Typical examples of this
             content in the FHIR specification are tables of contents, registries, examples,
             and implementer advice.</td> 

        </tr> 
        <tr> 
          <td style="white-space:nowrap">deprecated
            <a name="standards-status-deprecated"> </a> 
          </td> 
          <td> Deprecated</td> 
          This portion of the specification is provided for implementer assistance, and does not
             make rules that implementers are required to follow. Typical examples of this content
             in the FHIR specification are tables of contents, registries, examples, and implementer
             advice.

          <td> This portion of the specification is provided for implementer assistance, and does
             not make rules that implementers are required to follow. Typical examples of this
             content in the FHIR specification are tables of contents, registries, examples,
             and implementer advice.</td> 

        </tr> 
        <tr> 
          <td style="white-space:nowrap">external
            <a name="standards-status-external"> </a> 
          </td> 
          <td> External</td> 
          This is content that is managed outside the FHIR Specification, but included for implementer
             convenience.

          <td> This is content that is managed outside the FHIR Specification, but included for
             implementer convenience.</td> 

        </tr> 
      </table> 
    </div> 
  </text> 
  <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
    <valueCode value="fhir"/> 
  </extension> 
  <url value="http://hl7.org/fhir/standards-status"/> 
  <identifier> 
    <system value="urn:ietf:rfc:3986"/> 
    

    <value value="urn:oid:2.16.840.1.113883.4.642.4.1898"/> 
  </identifier> 
  

  <version value="5.0.0-ballot"/> 
  <name value="StandardsStatus"/> 
  
  

  <status value="draft"/> 
  <experimental value="false"/> 
  

  <caseSensitive value="true"/> 
  <content value="complete"/> 
  <concept> 
    <code value="draft"/> 
    <display value="Draft"/> 
    <definition value="This portion of the specification is not considered to be complete enough or sufficiently
     reviewed to be safe for implementation. It may have known issues or still be in the &quot;in
     development&quot; stage. It is included in the publication as a place-holder, to solicit
     feedback from the implementation community and/or to give implementers some insight as
     to functionality likely to be included in future versions of the specification. Content
     at this level should only be implemented by the brave or desperate and is very much &quot;use
     at your own risk&quot;. The content that is Draft that will usually be elevated to Trial
     Use once review and correction is complete after it has been subjected to ballot.

     reviewed to be safe for implementation. It may have known issues or still be in
     the &quot;in development&quot; stage. It is included in the publication as a place-holder,
     to solicit feedback from the implementation community and/or to give implementers
     some insight as to functionality likely to be included in future versions of the
     specification. Content at this level should only be implemented by the brave or
     desperate and is very much &quot;use at your own risk&quot;. The content that is
     Draft that will usually be elevated to Trial Use once review and correction is
     complete after it has been subjected to ballot."/> 

  </concept> 
  <concept> 
    <code value="normative"/> 
    <display value="Normative"/> 
    This content has been subject to review and production implementation in a wide variety
     of environments. The content is considered to be stable and has been 'locked', subjecting
     it to FHIR Inter-version Compatibility Rules. While changes are possible, they are expected
     to be infrequent and are tightly constrained. Compatibility Rules.

    <definition value="This content has been subject to review and production implementation in a wide
     variety of environments. The content is considered to be stable and has been 'locked',
     subjecting it to FHIR Inter-version Compatibility Rules. While changes are possible,
     they are expected to be infrequent and are tightly constrained. Compatibility Rules."/> 

  </concept> 
  <concept> 
    <code value="trial-use"/> 
    <display value="Trial-Use"/> 
    This content has been well reviewed and is considered by the authors to be ready for use
     in production systems. It has been subjected to ballot and approved as an official standard.
     However, it has not yet seen widespread use in production across the full spectrum of
     environments it is intended to be used in. In some cases, there may be documented known
     issues that require implementation experience to determine appropriate resolutions for.

    <definition value="This content has been well reviewed and is considered by the authors to be ready
     for use in production systems. It has been subjected to ballot and approved as
     an official standard. However, it has not yet seen widespread use in production
     across the full spectrum of environments it is intended to be used in. In some
     cases, there may be documented known issues that require implementation experience
     to determine appropriate resolutions for.


Future versions of FHIR may make significant changes to Trial Use content that are not
     compatible with previously published content.

Future versions of FHIR may make significant changes to Trial Use content that
     are not compatible with previously published content."/> 

  </concept> 
  <concept> 
    <code value="informative"/> 
    <display value="Informative"/> 
    This portion of the specification is provided for implementer assistance, and does not
     make rules that implementers are required to follow. Typical examples of this content
     in the FHIR specification are tables of contents, registries, examples, and implementer
     advice.

    <definition value="This portion of the specification is provided for implementer assistance, and does
     not make rules that implementers are required to follow. Typical examples of this
     content in the FHIR specification are tables of contents, registries, examples,
     and implementer advice."/> 

  </concept> 
  <concept> 
    <code value="deprecated"/> 
    <display value="Deprecated"/> 
    This portion of the specification is provided for implementer assistance, and does not
     make rules that implementers are required to follow. Typical examples of this content
     in the FHIR specification are tables of contents, registries, examples, and implementer
     advice.

    <definition value="This portion of the specification is provided for implementer assistance, and does
     not make rules that implementers are required to follow. Typical examples of this
     content in the FHIR specification are tables of contents, registries, examples,
     and implementer advice."/> 

  </concept> 
  <concept> 
    <code value="external"/> 
    <display value="External"/> 
    This is content that is managed outside the FHIR Specification, but included for implementer
     convenience.

    <definition value="This is content that is managed outside the FHIR Specification, but included for
     implementer convenience."/> 

  </concept> 


</

CodeSystem

>