4.3 CarePlan リソース
Resource CarePlan - Content4.3
Describes the intention of how one or more practitioners intend to deliver care for a particular patient for a period of time, possibly limited to care for a specific condition or set of conditions.
The resource name as it appears in a RESTful URL is [root]/careplan/
Care Plans are used in many of areas of healthcare with a variety of scopes. They can be as simple as a general practitioner keeping track of when their patient is next due for a tetanus immunization through to a detailed plan for an oncology patient covering diet, chemotherapy, radiation, lab work and counseling with detailed timing relationships, pre-conditions and goals.
This resource takes an intermediate approach. It captures basic details about who is involved and what actions are intended without dealing in discrete data about dependencies and timing relationships. These can be supported where necessary using the extension mechanisms.
Comments are welcome about the appropriateness of the proposed level of granularity, whether it's too much detail for what most systems need, or not sufficient for common essential use cases.
Resource Content4.3.1
<CarePlan xmlns="http://hl7.org/fhir"> <!-- from Resource: extension, narrative, and contained --> <identifier><!-- 0..1 Identifier ID for plan --></identifier> <patient><!-- 1..1 Resource(Patient) Who care plan is for --></patient> <status value="[code]"/><!-- 1..1 planned | active | ended --> <period><!-- 0..1 Period Time period plan covers --></period> <modified value="[dateTime]"/><!-- 0..1 When last updated --> <concern><!-- 0..* Resource(Condition) Health issues plan addresses --></concern> <participant> <!-- 0..* Who's involved in plan? --> <role><!-- 0..1 CodeableConcept Type of involvement --></role> <member><!-- 1..1 Resource(Practitioner|RelatedPerson|Patient|Organization) Who is involved --></member> </participant> <goal> <!-- 0..* Desired outcome of plan --> <description value="[string]"/><!-- 1..1 What's the desired outcome? --> <status value="[code]"/><!-- 0..1 in progress | achieved | sustaining | abandoned --> <notes value="[string]"/><!-- 0..1 Comments about the goal --> </goal> <activity> <!-- 0..* Action to occur as part of plan --> <category value="[code]"/><!-- 1..1 encounter | procedure | observation | + --> <code><!-- 0..1 CodeableConcept Detail type of activity --></code> <status value="[code]"/><!-- 0..1 not started | ongoing | suspended | completed | abandoned --> <prohibited value="[boolean]"/><!-- 1..1 Do NOT do --> <timing[x]><!-- 0..1 Schedule|Period|string When activity is to occur --></timing[x]> <location><!-- 0..1 Resource(Location) Where it should happen --></location> <performer><!-- 0..* Resource(Practitioner|Organization|RelatedPerson|Patient) Who's responsible? --></performer> <product><!-- 0..1 Resource(Medication|Substance) What's administered/supplied --></product> <dailyAmount><!-- 0..1 Quantity How much consumed/day? --></dailyAmount> <quantity><!-- 0..1 Quantity How much is administered/supplied/consumed --></quantity> <details value="[string]"/><!-- 0..1 Extra info on activity occurrence --> <actionTaken><!-- 0..* Resource(Any) Appointments, orders, etc. --></actionTaken> <notes value="[string]"/><!-- 0..1 Comments about the activity --> </activity> <notes value="[string]"/><!-- 0..1 Comments about the plan --> </CarePlan>
Alternate definitions: Schema/Schematron, Resource Profile
Terminology Bindings 4.3.1.1
Constraints4.3.1.2
- Inv-1: On CarePlan.activity: DailyDose can only be specified if activity category is drug or food (xpath on f:CarePlan/f:activity:(f:category/@value=('drug','diet')) = exists(f:dailyAmount))
- Inv-2: On CarePlan.activity: Quantity can only be specified if activity category is supply (xpath on f:CarePlan/f:activity:(f:category/@value=('supply')) = exists(f:quantity))
Open Issues4.3.2
- This resource combines the concepts of "Care Plan" and "Care Team" into a single resource. Is this appropriate?
- This specification leaves the specific relationship between activities in the care plan to textual description. Is more rigor required within the 80%?
Search Parameters 4.3.3
Search Parameters for RESTful searches. The standard parameters also apply. See Searching for more information.