Release 4B R5 Final QA

This page is part of the FHIR Specification (v4.3.0: R4B (v5.0.0-draft-final: Final QA Preview for R5 - STU see ballot notes ). 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

Activitydefinition-servicerequest-example

Example ActivityDefinition/heart-valve-replacement (Narrative)

Clinical Decision Support Work Group Maturity Level : N/A Standards Status : Informative Compartments : Not linked to any defined compartments

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

Generated Narrative Narrative: ActivityDefinition

Resource ActivityDefinition "heart-valve-replacement"

status : draft

description : Heart valve replacement

UseContexts

- Code Value[x]
* Age Range (Details: http://terminology.hl7.org/CodeSystem/usage-context-type code age = 'Age Range', stated as 'null') Adult (meshb.nlm.nih.gov#D000328)
* User Type (Details: http://terminology.hl7.org/CodeSystem/usage-context-type code user = 'User Type', stated as 'null') Physician ( SNOMED CT #309343006)

purpose : Describes the proposal to perform a Heart Valve replacement.

usage : This activity definition is used as the definition of a service request to perform a heart valve replacement. Elements that apply universally are defined here, while elements that apply to the specific setting of a referral within a particular order set are defined in the order set.

topic : Heart valve replacement ( SNOMED CT #34068001)

kind : ServiceRequest

code : Heart valve replacement ( SNOMED CT #34068001)

timing : Events: Now()

Locations

- location : Reference
* Location/1 "South Wing, second floor"

Participants

- Type Role
* practitioner Interventional Cardiology (provider-taxonomy#207RI0011X)

bodySite : Heart valve structure ( SNOMED CT #17401000)

 

 

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.