Release 5 R6 Ballot (1st Draft)

This page is part of the FHIR Specification (v5.0.0: R5 - STU v6.0.0-ballot1: Release 6 Ballot (1st 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 . Page versions: R5 R4B R4 R3

Example CompartmentDefinition/example (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 CompartmentDefinition .

Generated Narrative: CompartmentDefinition

Resource CompartmentDefinition "example"

StructureDefinition Work Group : fhir

url : http://hl7.org/fhir/CompartmentDefinition/example

name : EXAMPLE

title : E X A M P L E

status : draft

experimental : true

date : 2017-02-24

publisher : Health Level Seven HL7 International (FHIR Infrastructure) / FHIR Infrastructure

contact : [string]: http://hl7.org/fhir http://www.hl7.org/Special/committees/fiwg , http://www.hl7.org/Special/committees/fiwg/index.cfm

description : The set of resources associated with a particular Device (example with Communication and CommunicationRequest resourses only).

UseContexts

- Code Value[x]
* Clinical Focus (Details: http://terminology.hl7.org/CodeSystem/usage-context-type code focus = 'Clinical Focus', stated as 'null') Device ( All FHIR Types #Device)

purpose : Provides an example of a FHIR compartment definition based on the Device resource type.

code : Device

search : true

resource

code : Communication

param : sender, recipient

documentation : The device used as the message sender and recipient

resource

code : CommunicationRequest

param : sender, recipient

documentation : The device used as the message sender and recipient

 

 

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.