This page is part of the HL7 Terminology (v6.1.0: Release) based on FHIR (HL7® FHIR® Standard) v5.0.0. This is the current published version. For a full list of available versions, see the Directory of published versions
: PlanDefinitionType - TTL Representation
Raw ttl | Download
@prefix fhir: <http://hl7.org/fhir/> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
# - resource -------------------------------------------------------------------
a fhir:CodeSystem ;
fhir:nodeRole fhir:treeRoot ;
fhir:id [ fhir:v "plan-definition-type"] ; #
fhir:meta [
fhir:lastUpdated [ fhir:v "2024-04-24T00:00:00+00:00"^^xsd:dateTime ]
] ; #
fhir:text [
fhir:status [ fhir:v "generated" ] ;
fhir:div "<div xmlns=\"http://www.w3.org/1999/xhtml\"><p class=\"res-header-id\"><b>Generated Narrative: CodeSystem plan-definition-type</b></p><a name=\"plan-definition-type\"> </a><a name=\"hcplan-definition-type\"> </a><a name=\"plan-definition-type-en-US\"> </a><div style=\"display: inline-block; background-color: #d9e0e7; padding: 6px; margin: 4px; border: 1px solid #8da1b4; border-radius: 5px; line-height: 60%\"><p style=\"margin-bottom: 0px\">Last updated: 2024-04-24 00:00:00+0000</p></div><p>This case-sensitive code system <code>http://terminology.hl7.org/CodeSystem/plan-definition-type</code> defines the following codes:</p><table class=\"codes\"><tr><td style=\"white-space:nowrap\"><b>Code</b></td><td><b>Display</b></td><td><b>Definition</b></td></tr><tr><td style=\"white-space:nowrap\">order-set<a name=\"plan-definition-type-order-set\"> </a></td><td>Order Set</td><td>A pre-defined and approved group of orders related to a particular clinical condition (e.g. hypertension treatment and monitoring) or stage of care (e.g. hospital admission to Coronary Care Unit). An order set is used as a checklist for the clinician when managing a patient with a specific condition. It is a structured collection of orders relevant to that condition and presented to the clinician in a computerized provider order entry (CPOE) system.</td></tr><tr><td style=\"white-space:nowrap\">clinical-protocol<a name=\"plan-definition-type-clinical-protocol\"> </a></td><td>Clinical Protocol</td><td>Defines a desired/typical sequence of clinical activities including preconditions, triggers and temporal relationships.</td></tr><tr><td style=\"white-space:nowrap\">eca-rule<a name=\"plan-definition-type-eca-rule\"> </a></td><td>ECA Rule</td><td>A decision support rule of the form [on Event] if Condition then Action. It is intended to be a shareable, computable definition of actions that should be taken whenever some condition is met in response to a particular event or events.</td></tr><tr><td style=\"white-space:nowrap\">workflow-definition<a name=\"plan-definition-type-workflow-definition\"> </a></td><td>Workflow Definition</td><td>Defines the steps for a group of one or more systems in an event flow process along with the step constraints, sequence, pre-conditions and decision points to complete a particular objective.</td></tr></table></div>"
] ; #
fhir:extension ( [
fhir:url [ fhir:v "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg"^^xsd:anyURI ] ;
fhir:value [ fhir:v "cds" ]
] [
fhir:url [ fhir:v "http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm"^^xsd:anyURI ] ;
fhir:value [ fhir:v "2"^^xsd:integer ]
] ) ; #
fhir:url [ fhir:v "http://terminology.hl7.org/CodeSystem/plan-definition-type"^^xsd:anyURI] ; #
fhir:identifier ( [
fhir:system [ fhir:v "urn:ietf:rfc:3986"^^xsd:anyURI ] ;
fhir:value [ fhir:v "urn:oid:2.16.840.1.113883.4.642.1.1245" ]
] ) ; #
fhir:version [ fhir:v "1.0.1"] ; #
fhir:name [ fhir:v "PlanDefinitionType"] ; #
fhir:title [ fhir:v "PlanDefinitionType"] ; #
fhir:status [ fhir:v "active"] ; #
fhir:experimental [ fhir:v "false"^^xsd:boolean] ; #
fhir:date [ fhir:v "2024-04-24T00:00:00+00:00"^^xsd:dateTime] ; #
fhir:publisher [ fhir:v "Health Level Seven International"] ; #
fhir:contact ( [
( fhir:telecom [
fhir:system [ fhir:v "url" ] ;
fhir:value [ fhir:v "http://hl7.org" ] ] [
fhir:system [ fhir:v "email" ] ;
fhir:value [ fhir:v "hq@HL7.org" ] ] )
] ) ; #
fhir:description [ fhir:v "The type of PlanDefinition."] ; #
fhir:copyright [ fhir:v "This material derives from the HL7 Terminology (THO). THO is copyright ©1989+ Health Level Seven International and is made available under the CC0 designation. For more licensing information see: https://terminology.hl7.org/license"] ; #
fhir:caseSensitive [ fhir:v "true"^^xsd:boolean] ; #
fhir:valueSet [
fhir:v "http://terminology.hl7.org/ValueSet/plan-definition-type"^^xsd:anyURI ;
fhir:link <http://terminology.hl7.org/ValueSet/plan-definition-type>
] ; #
fhir:content [ fhir:v "complete"] ; #
fhir:concept ( [
fhir:code [ fhir:v "order-set" ] ;
fhir:display [ fhir:v "Order Set" ] ;
fhir:definition [ fhir:v "A pre-defined and approved group of orders related to a particular clinical condition (e.g. hypertension treatment and monitoring) or stage of care (e.g. hospital admission to Coronary Care Unit). An order set is used as a checklist for the clinician when managing a patient with a specific condition. It is a structured collection of orders relevant to that condition and presented to the clinician in a computerized provider order entry (CPOE) system." ]
] [
fhir:code [ fhir:v "clinical-protocol" ] ;
fhir:display [ fhir:v "Clinical Protocol" ] ;
fhir:definition [ fhir:v "Defines a desired/typical sequence of clinical activities including preconditions, triggers and temporal relationships." ]
] [
fhir:code [ fhir:v "eca-rule" ] ;
fhir:display [ fhir:v "ECA Rule" ] ;
fhir:definition [ fhir:v "A decision support rule of the form [on Event] if Condition then Action. It is intended to be a shareable, computable definition of actions that should be taken whenever some condition is met in response to a particular event or events." ]
] [
fhir:code [ fhir:v "workflow-definition" ] ;
fhir:display [ fhir:v "Workflow Definition" ] ;
fhir:definition [ fhir:v "Defines the steps for a group of one or more systems in an event flow process along with the step constraints, sequence, pre-conditions and decision points to complete a particular objective." ]
] ) . #
|
|
Propose a change