This
page
is
part
of
the
FHIR
Specification
(v3.0.2:
(v4.0.1:
R4
-
Mixed
Normative
and
STU
3).
)
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
R4
R3
R2
| Vocabulary Work Group | Maturity Level : N/A |
|
Raw XML ( canonical form + also see XML Format Specification )
Definition for Value SetCare Plan Category
<?xml version="1.0" encoding="UTF-8"?> <ValueSet xmlns="http://hl7.org/fhir"> <id value="care-plan-category"/> <meta><lastUpdated value="2019-11-01T09:29:23.356+11:00"/> <profile value="http://hl7.org/fhir/StructureDefinition/shareablevalueset"/> </meta> <text> <status value="generated"/> <div xmlns="http://www.w3.org/1999/xhtml"> <h2> Care Plan Category</h2> <div> <p> Example codes indicating the category a care plan falls within. Note that these are inno way complete and may not even be appropriate for some uses.no way complete and might not even be appropriate for some uses.</p> </div> <p>This value set includes content from SNOMED CT, which is copyright © 2002+ International Health Terminology Standards Development Organisation (IHTSDO), and distributed by agreement between IHTSDO and HL7. Implementer use of SNOMED CT is not covered by this agreement.<b> Copyright Statement:</b> </p> <div> <p> This resource includes content from SNOMED Clinical Terms® (SNOMED CT®) which is copyright of the International Health Terminology Standards Development Organisation (IHTSDO). Implementers of these specifications must have the appropriate SNOMED CT Affiliate license - for more information contact http://www.snomed.org/snomed-ct/get-snomed-ct or info@snomed.org</p> </div> <p> This value set includes codes from the following code systems:</p> <ul> <li> Include codes from <a href="http://www.snomed.org/"> <code> http://snomed.info/sct</code>where concept is-a 278448002 (Care plan)</a> where concept is-a 734163000 (Care plan) </li> </ul> </div> </text><extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg"> <valueCode value="pc"/> </extension> <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status"> <valueCode value="draft"/> </extension> <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm"> <valueInteger value="1"/> </extension><url value="http://hl7.org/fhir/ValueSet/care-plan-category"/> <identifier> <system value="urn:ietf:rfc:3986"/><value value="urn:oid:2.16.840.1.113883.4.642.3.148"/> </identifier><version value="4.0.1"/> <name value="CarePlanCategory"/> <title value="Care Plan Category"/> <status value="draft"/><experimental value="false"/> <date value="2019-11-01T09:29:23+11:00"/> <publisher value="HL7 International - Patient Care WG"/> <contact> <telecom> <system value="url"/> <value value="http://www.hl7.org/Special/committees/patientcare/"/> </telecom> </contact> <description value="Example codes indicating the category a care plan falls within. Note that these are inno way complete and may not even be appropriate for some uses. This value set includes content from SNOMED CT, which is copyright © 2002+ International Health Terminology Standards Development Organisation (IHTSDO), and distributed by agreement between IHTSDO and HL7. Implementer use of SNOMED CT is not covered by this agreement.no way complete and might not even be appropriate for some uses."/> <copyright value="This resource includes content from SNOMED Clinical Terms® (SNOMED CT®) which is copyright of the International Health Terminology Standards Development Organisation (IHTSDO). Implementers of these specifications must have the appropriate SNOMED CT Affiliate license - for more information contact http://www.snomed.org/snomed-ct/get-snomed-ct or info@snomed.org"/> <compose> <include> <system value="http://snomed.info/sct"/> <filter> <property value="concept"/> <op value="is-a"/><value value="734163000"/> </filter> </include> </compose> </ ValueSet >
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.