Release 5 R6 Ballot (2nd Draft)

This page is part of the FHIR Specification (v5.0.0: R5 - STU v6.0.0-ballot2: Release 6 Ballot (2nd Draft) (see Ballot Notes ). This is the The current published version in it's permanent home (it will always be available at this URL). is 5.0.0 . For a full list of available versions, see the Directory of published versions

Example Requirements/example2 (Narrative)

FHIR Infrastructure Work Group Maturity Level : N/A Standards Status : Informative Compartments : No defined compartments

This is the narrative for the resource. See also the XML , JSON or Turtle format. This example conforms to the profile Requirements .

Generated Narrative: Requirements example2

Resource Requirements "example2"

url : http://hl7.org/fhir/Requirements/example2

identifier : id: urn:oid:2.16.840.1.113883.4.642.18.2 Uniform Resource Identifier (URI) /urn:oid:2.16.840.1.113883.4.642.18.2

name : ExampleRequirements2

title : Example Requirements Set 2

status : active

date : 2021-11-02T14:31:30.239Z

publisher : HL7 International / FHIR Infrastructure

contact : http://www.hl7.org/Special/committees/fiwg

description :

Example Requirements Set 2

derivedFrom : http://hl7.org/fhir/Requirements/example2

actor : http://hl7.org/fhir/ActorDefinition/server

statement

key : 44595579-fa13-42a5-bd24-0515cde96963

label : requirement-B1

conformance : SHOULD

requirement :

Operations based on the SNOMED-CT should use the current version within 24 hours of each release

source : : Lloyd Mackenzie

statement

key : 46f77dcd-d51e-4738-b61f-22506d0cb0ac

label : requirement-2/a

conformance : SHALL

requirement :

ValueSet expansion and validation SHALL have the same result whether or not underlying CodeSystem resources have relationships represented explicitly as properties or implicitly using the CodeSystem resource hierarchy

source : : Robert Hausam

 

Other examples that reference this example: Requirements/Second Requirements Example  

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.