Release 4 5

This page is part of the FHIR Specification (v4.0.1: R4 (v5.0.0: R5 - Mixed Normative and STU ) ). This is the current published version in it's permanent home (it will always be available at this URL). The current version which supercedes this version is 5.0.0 . For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3

Graphdefinition-example

Example GraphDefinition/example (Narrative)

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

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

Generated Narrative with Details Narrative: GraphDefinition

id : example

Resource GraphDefinition "example"

url : http://h7.org/fhir/GraphDefinition/example

name : DocumentGenerationTemplate

title : Document Generation Template

status : draft

date : 04/08/2015 2015-08-04

publisher : FHIR Project

contact : http://hl7.org/fhir

description : Specify to include list references when generating a document using the $document operation

start : comp1

node

nodeId : comp1

description : The base composition

type : Composition

profile : Clinical Document

link node

path nodeId : Composition.section.entry list1

description : Link A list resource that a section entry reference points to

type : List

target node

nodeId : resN

description : Generic resource that's the target of a list reference

type : List Resource

link

description : Link from Composition.section to list

sourceId : comp1

path : Composition.section.entry

targetId : list1

Compartments

- Use Code Rule Rule Code
* requirement requires Patient identical identical Patient

link

description : Include any list entries

sourceId : list1

path : List.entry.item

targetId : resN

Links Compartments

- Use Rule Code
* requires identical Patient

 

 

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.