Release 5 FHIR CI-Build

This page is part of the Continuous Integration Build of FHIR Specification (v5.0.0: R5 - STU ). This is the current published version in it's permanent home (it will always (will be available incorrect/inconsistent at this URL). For a full list of available versions, see times).
See the Directory of published versions . Page versions: R5 R4B R4 R3

Example GuidanceResponse/example (Narrative)

Maturity Level : N/A
Responsible Owner: Clinical Decision Support Work Group Standards Status : Informative Compartments : Group , Patient

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


Generated Narrative: GuidanceResponse example

Resource GuidanceResponse "example"

requestIdentifier : id: guidanceRequest1 http://example.org /guidanceRequest1

identifier : id: guidanceResponse1 http://example.org /guidanceResponse1

module : http://someguidelineprovider.org/radiology-appropriateness-guidelines.html

status : success Success

subject : Patient/example Jim Male, DoB: 1974-12-25 ( Medical record number (use: usual, period: 2001-05-06 --> (ongoing))) "Peter CHALMERS"

encounter : Encounter/example Encounter: status = in-progress; class = inpatient encounter; subjectStatus = Receiving Care

occurrenceDateTime : 2017-03-10T16:02:00Z

performer : Device/software

Reasons

- Concept
* Guideline Appropriate Ordering Assessment ()

outputParameters : Parameters: score, item-assessed, device, guideline-followed


parameter Generated Narrative: Parameters #outputParameters1

name : score value : 7

Parameters

parameter name : name : name :
score 7
item-assessed value : CT, head, wo iv Computed tomography, head or brain; without contrast ( Current Procedural Terminology (CPT®) #70450) material parameter
device value : Device/software parameter
guideline-followed value : http://someguidelineprovider.org/radiology-appropriateness-guidelines.html

 

 

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.