FHIR Release 3 (STU) CI-Build

This page is part of the FHIR Specification (v3.0.2: STU 3). The current version which supercedes this version is 5.0.0 . For a full list Continuous Integration Build of available versions, see FHIR (will be incorrect/inconsistent at times).
See the Directory of published versions . Page versions: R5 R4B R4 R3

Compartmentdefinition-example

Example CompartmentDefinition/example (Narrative)

Maturity Level : N/A
Responsible Owner: FHIR Infrastructure Work Group Ballot Standards Status : Informative Compartments : Not linked to any No defined compartments

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

Generated Narrative with Details Narrative: CompartmentDefinition example

id StructureDefinition Work Group : example fhir

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

name : EXAMPLE

title : Base FHIR compartment definition for Device(example) EXAMPLE

status : draft Draft

experimental : true

date : 24/02/2017 2017-02-24

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

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

description :

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

UseContexts

- Code Value[x]
* UsageContextType: focus (Clinical Focus) Device

purpose :

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

useContext : jurisdiction : United States of America (the) (Details : {urn:iso:std:iso:3166 code 'US' = 'United States', given as 'United States of America (the)'})

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.