Release 5 Ballot

This page is part of the FHIR Specification (v5.0.0-ballot: FHIR R5 Ballot Preview). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions

Example Requirements/example1 (XML)

FHIR Infrastructure Work GroupMaturity Level: N/AStandards Status: InformativeCompartments: Not linked to any defined compartments

Raw XML (canonical form + also see XML Format Specification)

Jump past Narrative

null (id = "example1")

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

<Requirements xmlns="http://hl7.org/fhir">
  <id value="example1"/> 
  <text> <status value="generated"/> <div xmlns="http://www.w3.org/1999/xhtml"><p> <b> Generated Narrative: Requirements</b> <a name="example1"> </a> </p> <div style="display: inline-block; background-color: #d9e0e7; padding: 6px; margin: 4px; border: 1px
       solid #8da1b4; border-radius: 5px; line-height: 60%"><p style="margin-bottom: 0px">Resource Requirements &quot;example1&quot; </p> </div> <p> <b> url</b> : <a href="http://hl7.org/fhir/Requirements/example1">http://hl7.org/fhir/Requirements/example1</a> </p> <p> <b> identifier</b> : id: urn:oid:2.16.840.1.113883.4.642.18.1</p> <p> <b> name</b> : ExampleRequirements1</p> <p> <b> title</b> : Example Requirements Set 1</p> <p> <b> status</b> : active</p> <p> <b> date</b> : 2021-11-02T14:31:30.239Z</p> <p> <b> actor</b> : <a href="http://hl7.org/fhir/ActorDefinition/server">http://hl7.org/fhir/ActorDefinition/server</a> </p> <blockquote> <p> <b> statement</b> </p> <p> <b> key</b> : req-1</p> <p> <b> conformance</b> : <span title="  
    &lt;label value=&quot;requirement-1&quot;/&gt;
    since this is commented out, it's simply 'req-1'
     ">SHALL</span> </p> <p> <b> requirement</b> : The server SHALL support expanding value sets</p> <p> <b> satisfiedBy</b> : <a href="http://hl7.org/fhir/terminology-service.html#expand">http://hl7.org/fhir/terminology-service.html#expand</a> </p> <p> <b> source</b> : <span> : Grahame Grieve</span> </p> </blockquote> <blockquote> <p> <b> statement</b> </p> <p> <b> key</b> : 46f77dcd-d51e-4738-b61f-22506d0cb0ac</p> <p> <b> label</b> : requirement-2</p> <p> <b> conformance</b> : SHALL</p> <p> <b> requirement</b> : Operations based on the codeSystem resource SHALL have the same result whether or not
           the relationships are represented explicitly as properties or implicitly using the CodeSystem
           resource hierarchy</p> <p> <b> source</b> : <span> : Jose Costa Teixeira</span> </p> </blockquote> </div> </text> <url value="http://hl7.org/fhir/Requirements/example1"/> 
  <identifier> 
    <system value="urn:ietf:rfc:3986"/> 
    <value value="urn:oid:2.16.840.1.113883.4.642.18.1"/> 
  </identifier> 
  <name value="ExampleRequirements1"/> 
  <title value="Example Requirements Set 1"/> 
  <status value="active"/> 
  <date value="2021-11-02T14:31:30.239Z"/> 
  <actor value="http://hl7.org/fhir/ActorDefinition/server"/> 

  <!--    first requirement, which is satisfied by the base spec    -->
  <statement> 
    <key value="req-1"/> 
    <!--    
    <label value="requirement-1"/>
    since this is commented out, it's simply 'req-1'
       -->
    <conformance value="SHALL"/> 
    <requirement value="The server SHALL support expanding value sets"/> 
    <satisfiedBy value="http://hl7.org/fhir/terminology-service.html#expand"/> 
    <source> 
      <display value="Grahame Grieve"/> 
    </source> 
  </statement> 

  <!--    second requirement    -->
  <statement> 
    <key value="46f77dcd-d51e-4738-b61f-22506d0cb0ac"/> 
    <label value="requirement-2"/> 
    <conformance value="SHALL"/> 
    <requirement value="Operations based on the codeSystem resource SHALL have the same result whether or not
     the relationships are represented explicitly as properties or implicitly using the CodeSystem
     resource hierarchy"/> 
    <source> 
      <display value="Jose Costa Teixeira"/> 
    </source> 
  </statement> 
</Requirements> 

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.