This is the Continuous Integration Build of FHIR (will be incorrect/inconsistent at times).
See the Directory of published versions
Example Requirements/example1 (XML)
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="extensions"/> <div xmlns="http://www.w3.org/1999/xhtml"><p> <b> Generated Narrative: Requirements</b> <a name="example1"> </a> <a name="hcexample1"> </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 "example1" </p> </div> <p> <b> StructureDefinition Work Group</b> : fhir</p> <p> <b> url</b> : <code> http://hl7.org/fhir/Requirements/example1</code> </p> <p> <b> identifier</b> : <a href="http://terminology.hl7.org/5.5.0/NamingSystem-uri.html" title="As defined by RFC 3986 (http://www.ietf.org/rfc/rfc3986.txt)(with many schemes
defined in many RFCs). For OIDs and UUIDs, use the URN form (urn:oid:(note: lowercase)
and urn:uuid:). See http://www.ietf.org/rfc/rfc3001.txt and http://www.ietf.org/rfc/rfc4122.t
xt
This oid is used as an identifier II.root to indicate the the extension is an absolute
URI (technically, an IRI). Typically, this is used for OIDs and GUIDs. Note that
when this OID is used with OIDs and GUIDs, the II.extension should start with urn:oid
or urn:uuid:
Note that this OID is created to aid with interconversion between CDA and FHIR
- FHIR uses urn:ietf:rfc:3986 as equivalent to this OID. URIs as identifiers appear
more commonly in FHIR.
This OID may also be used in CD.codeSystem.">URI</a> /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> publisher</b> : HL7 International / FHIR Infrastructure</p> <p> <b> contact</b> : </p> <p> <b> description</b> : Example Requirements Set 1</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> : SHALL</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> <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg"><valueCode value="fhir"/> </extension>
<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"/>
<publisher value="HL7 International / FHIR Infrastructure"/>
<contact>
<telecom>
<system value="url"/>
</telecom>
</contact>
<description value="Example Requirements Set 1"/>
<actor value="http://hl7.org/fhir/ActorDefinition/server"/>
<statement>
<key value="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>
<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.