Definitions for the ehealth-careplan Profile.
1. CarePlan | |
Definition | Describes the intention of how one or more practitioners intend to deliver care for a particular patient, group or community for a period of time, possibly limited to care for a specific condition or set of conditions. |
Control | 0..* |
Alternate Names | Care Team |
Invariants | Defined on this element dom-1: If the resource is contained in another resource, it SHALL NOT contain any narrative (: contained.text.empty()) dom-2: If the resource is contained in another resource, it SHALL NOT contain nested Resources (: contained.contained.empty()) dom-3: If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource (: contained.where(('#'+id in %resource.descendants().reference).not()).empty()) dom-4: If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated (: contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()) |
2. CarePlan.id | |
Definition | The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. |
Control | 0..1 |
Type | id |
Comments | The only time that a resource does not have an id is when it is being submitted to the server using a create operation. |
3. CarePlan.meta | |
Definition | The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content may not always be associated with version changes to the resource. |
Control | 0..1 |
Type | Meta |
4. CarePlan.implicitRules | |
Definition | A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. |
Control | 0..1 |
Type | uri |
Is Modifier | true |
Comments | Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation. |
5. CarePlan.language | |
Definition | The base language in which the resource is written. |
Control | 0..1 |
Binding | A human language. The codes SHALL be taken from Common Languages; other codes may be used where these codes are not suitable Max Binding: All Languages |
Type | code |
Comments | Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute). |
6. CarePlan.text | |
Definition | A human-readable narrative that contains a summary of the resource, and may be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety. |
Control | 0..1 This element is affected by the following invariants: dom-1 |
Type | Narrative |
Alternate Names | narrative, html, xhtml, display |
Comments | Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded in formation is added later. |
7. CarePlan.contained | |
Definition | These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope. |
Control | 0..* |
Type | Resource |
Alternate Names | inline resources, anonymous resources, contained resources |
Comments | This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. |
8. CarePlan.extension | |
Definition | An Extension |
Control | 0..* |
Type | Extension |
Slicing | This element introduces a set of slices on CarePlan.extension. The slices are unordered and Open, and can be differentiated using the following discriminators:
|
9. CarePlan.extension:statusHistory | |
SliceName | statusHistory |
Definition | History of status changes |
Control | 0..* This element is affected by the following invariants: ele-1 |
Type | Extension(statusHistory) (Extension Type: Choice of: base64Binary, boolean, code, date, dateTime, decimal, id, instant, integer, markdown, oid, positiveInt, string, time, unsignedInt, uri, Address, Age, Annotation, Attachment, CodeableConcept, Coding, ContactPoint, Count, Distance, Duration, HumanName, Identifier, Money, Period, Quantity, Range, Ratio, Reference, SampledData, Signature, Timing, Meta) |
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() | (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists()) |
10. CarePlan.extension:teamHistory | |
SliceName | teamHistory |
Definition | An Extension |
Control | 0..* This element is affected by the following invariants: ele-1 |
Type | Extension(teamHistory) (Extension Type: Choice of: base64Binary, boolean, code, date, dateTime, decimal, id, instant, integer, markdown, oid, positiveInt, string, time, unsignedInt, uri, Address, Age, Annotation, Attachment, CodeableConcept, Coding, ContactPoint, Count, Distance, Duration, HumanName, Identifier, Money, Period, Quantity, Range, Ratio, Reference, SampledData, Signature, Timing, Meta) |
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() | (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists()) |
11. CarePlan.modifierExtension | |
Definition | May be used to represent additional information that is not part of the basic definition of the resource, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. |
Control | 0..* |
Type | Extension |
Is Modifier | true |
Alternate Names | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
12. CarePlan.identifier | |
Definition | This records identifiers associated with this care plan that are defined by business processes and/or used to refer to it when a direct URL reference to the resource itself is not appropriate (e.g. in CDA documents, or in written / printed documentation). |
Note | This is a business identifier, not a resource identifier (see discussion) |
Control | 0..* |
Type | Identifier |
Requirements | Need to allow connection to a wider workflow. |
13. CarePlan.definition | |
Definition | PlanDefinition used as template for this CarePlan |
Control | 1..1 |
Type | Reference(ehealth-plandefinition | ehealth-questionnaire) |
14. CarePlan.basedOn | |
Definition | A care plan that is fulfilled in whole or in part by this care plan. |
Control | 0..0 |
Type | Reference(CarePlan) |
Requirements | Allows tracing of the care plan and tracking whether proposals/recommendations were acted upon. |
Alternate Names | fulfills |
15. CarePlan.replaces | |
Definition | Completed or terminated care plan whose function is taken by this new care plan. |
Control | 0..0 |
Type | Reference(CarePlan) |
Requirements | Allows tracing the continuation of a therapy or administrative process instantiated through multiple care plans. |
Alternate Names | supersedes |
Comments | The replacement could be because the initial care plan was immediately rejected (due to an issue) or because the previous care plan was completed, but the need for the action described by the care plan remains ongoing. |
16. CarePlan.partOf | |
Definition | A larger care plan of which this particular care plan is a component or step. |
Control | 0..1 |
Type | Reference(ehealth-careplan) |
Comments | Each care plan is an independent request, such that having a care plan be part of another care plan can cause issues with cascading statuses. As such, this element is still being discussed. |
17. CarePlan.status | |
Definition | Indicates whether the plan is currently being acted upon, represents future intentions or is now a historical record. |
Control | 1..1 |
Binding | Indicates whether the plan is currently being acted upon, represents future intentions or is now a historical record. The codes SHALL be taken from CarePlanStatus |
Type | code |
Is Modifier | true |
Requirements | Allows clinicians to determine whether the plan is actionable or not. |
Comments | The unknown code is not to be used to convey other statuses. The unknown code should be used when one of the statuses applies, but the authoring system doesn't know the current state of the care plan. This element is labeled as a modifier because the status contains the code entered-in-error] that marks the plan as not currently valid. |
18. CarePlan.intent | |
Definition | Indicates the level of authority/intentionality associated with the care plan and where the care plan fits into the workflow chain. |
Control | 1..1 |
Binding | Codes indicating the degree of authority/intentionality associated with a care plan The codes SHALL be taken from CarePlanIntent |
Type | code |
Is Modifier | true |
Requirements | Proposals/recommendations, plans and orders all use the same structure and can exist in the same fulfillment chain. |
Comments | This element is labeled as a modifier because the intent alters when and how the resource is actually applicable. |
19. CarePlan.category | |
Definition | Type of plan (Care Plan Category) |
Control | 0..* |
Binding | The codes SHALL be taken from Careplan Category |
Type | CodeableConcept |
Requirements | Used for filtering what plan(s) are retrieved and displayed to different types of users. |
Comments | There may be multiple axis of categorization and one plan may serve multiple purposes. In some cases, this may be redundant with references to CarePlan.concern. |
20. CarePlan.title | |
Definition | Human-friendly name for the CarePlan. |
Control | 0..1 |
Type | string |
21. CarePlan.description | |
Definition | A description of the scope and nature of the plan. |
Control | 0..1 |
Type | string |
Requirements | Provides more detail than conveyed by category. |
22. CarePlan.subject | |
Definition | Identifies the patient or group whose intended care is described by the plan. |
Control | 1..1 |
Type | Reference(ehealth-patient) |
Alternate Names | patient |
23. CarePlan.context | |
Definition | Identifies the original context in which this particular CarePlan was created. |
Control | 1..1 |
Type | Reference(ehealth-episodeofcare) |
Alternate Names | encounter |
Comments | Activities conducted as a result of the care plan may well occur as part of other encounters/episodes. |
24. CarePlan.period | |
Definition | Indicates when the plan did (or is intended to) come into effect and end. |
Control | 1..1 |
Type | Period |
Requirements | Allows tracking what plan(s) are in effect at a particular time. |
Alternate Names | timing |
Comments | Any activities scheduled as part of the plan should be constrained to the specified period regardless of whether the activities are planned within a single encounter/episode or across multiple encounters/episodes (e.g. the longitudinal management of a chronic condition). |
25. CarePlan.author | |
Definition | Identifies the individual(s) or ogranization who is responsible for the content of the care plan. |
Control | 0..* |
Type | Reference(ehealth-patient | ehealth-practitioner | ehealth-relatedperson | ehealth-organization | ehealth-careteam) |
Comments | Collaborative care plans may have multiple authors. |
26. CarePlan.careTeam | |
Definition | Identifies all people and organizations who are expected to be involved in the care envisioned by this plan. |
Control | 0..* |
Type | Reference(ehealth-careteam) |
Requirements | Allows representation of care teams, helps scope care plan. In some cases may be a determiner of access permissions. |
27. CarePlan.addresses | |
Definition | Identifies the conditions/problems/concerns/diagnoses/etc. whose management and/or mitigation are handled by this plan. |
Control | 1..1 |
Type | Reference(ehealth-condition) |
Requirements | Links plan to the conditions it manages. The element can identify risks addressed by the plan as well as active conditions. (The Condition resource can include things like "at risk for hypertension" or "fall risk".) Also scopes plans - multiple plans may exist addressing different concerns. |
Comments | Condition.code is inherited from PlanDefinition.useContext.valueCodeableConcept for the code: focus. The Condition is a contained resource in this context. |
28. CarePlan.supportingInfo | |
Definition | Identifies portions of the patient's record that specifically influenced the formation of the plan. These might include co-morbidities, recent procedures, limitations, recent assessments, etc. |
Control | 0..* |
Type | Reference(Resource) |
Requirements | Identifies barriers and other considerations associated with the care plan. |
Comments | Use "concern" to identify specific conditions addressed by the care plan. |
29. CarePlan.goal | |
Definition | Describes the intended objective(s) of carrying out the care plan. |
Control | 0..* |
Type | Reference(Goal) |
Requirements | Provides context for plan. Allows plan effectiveness to be evaluated by clinicians. |
Comments | Goal can be achieving a particular change or merely maintaining a current state or even slowing a decline. |
30. CarePlan.activity | |
Definition | Identifies a planned action to occur as part of the plan. For example, a medication to be used, lab tests to perform, self-monitoring, education, etc. |
Control | 0..* |
Type | BackboneElement |
Requirements | Allows systems to prompt for performance of planned activities, and validate plans against best practice. |
Invariants | Defined on this element cpl-3: Provide a reference or detail, not both (: detail.empty() or reference.empty()) ele-1: All FHIR elements must have a @value or children (: hasValue() | (children().count() > id.count())) |
31. CarePlan.activity.id | |
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Control | 0..1 |
Type | string |
32. CarePlan.activity.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. |
Control | 0..* |
Type | Extension |
Alternate Names | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
33. CarePlan.activity.modifierExtension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. |
Control | 0..* |
Type | Extension |
Is Modifier | true |
Alternate Names | extensions, user content, modifiers |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
34. CarePlan.activity.outcomeCodeableConcept | |
Definition | Identifies the outcome at the point when the status of the activity is assessed. For example, the outcome of an education activity could be patient understands (or not). |
Control | 0..* |
Binding | Identifies the results of the activity For example codes, see Care Plan Activity Outcome |
Type | CodeableConcept |
Comments | Note that this should not duplicate the activity status (e.g. completed or in progress). |
35. CarePlan.activity.outcomeReference | |
Definition | Details of the outcome or action resulting from the activity. The reference to an "event" resource, such as Procedure or Encounter or Observation, is the result/outcome of the activity itself. The activity can be conveyed using CarePlan.activity.detail OR using the CarePlan.activity.reference (a reference to a “request” resource). |
Control | 0..* |
Type | Reference(Resource) |
Requirements | Links plan to resulting actions. |
Comments | The activity outcome is independent of the outcome of the related goal(s). For example, if the goal is to achieve a target body weight of 150 lb and an activity is defined to diet, then the activity outcome could be calories consumed whereas the goal outcome is an observation for the actual body weight measured. |
36. CarePlan.activity.progress | |
Definition | Notes about the adherence/status/progress of the activity. |
Control | 0..* |
Type | Annotation |
Requirements | Can be used to capture information about adherence, progress, concerns, etc. |
Comments | This element should NOT be used to describe the activity to be performed - that occurs either within the resource pointed to by activity.detail.reference or in activity.detail.description. |
37. CarePlan.activity.progress.id | |
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Control | 0..1 |
Type | string |
38. CarePlan.activity.progress.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. |
Control | 0..* |
Type | Extension |
Alternate Names | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Slicing | This element introduces a set of slices on CarePlan.activity.progress.extension. The slices are unordered and Open, and can be differentiated using the following discriminators:
|
39. CarePlan.activity.progress.author[x] | |
Definition | The individual responsible for making the annotation. |
Control | 0..1 |
Type | Choice of: Reference(ehealth-practitioner | ehealth-patient | ehealth-relatedperson), string |
[x] Note | See Choice of Data Types for further information about how to use [x] |
40. CarePlan.activity.progress.time | |
Definition | Indicates when this particular annotation was made. |
Control | 0..1 |
Type | dateTime |
41. CarePlan.activity.progress.text | |
Definition | The text of the annotation. |
Control | 1..1 |
Type | string |
42. CarePlan.activity.reference | |
Definition | The details of the proposed activity represented in a specific resource. |
Control | 1..1 This element is affected by the following invariants: cpl-3 |
Type | Reference(ehealth-procedurerequest) |
Requirements | Details in a form consistent with other applications and contexts of use. |
Comments | Standard extension exists (goal-pertainstogoal) that allows goals to be referenced from any of the referenced resources in CarePlan.activity.reference. |
43. CarePlan.activity.detail | |
Definition | A simple summary of a planned activity suitable for a general care plan system (e.g. form driven) that doesn't know about specific resources such as procedure etc. |
Control | 0..1 This element is affected by the following invariants: cpl-3 |
Type | BackboneElement |
Requirements | Details in a simple form for generic care plan systems. |
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() | (children().count() > id.count())) |
44. CarePlan.activity.detail.id | |
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Control | 0..1 |
Type | string |
45. CarePlan.activity.detail.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. |
Control | 0..* |
Type | Extension |
Alternate Names | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
46. CarePlan.activity.detail.modifierExtension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. |
Control | 0..* |
Type | Extension |
Is Modifier | true |
Alternate Names | extensions, user content, modifiers |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
47. CarePlan.activity.detail.category | |
Definition | High-level categorization of the type of activity in a care plan. |
Control | 0..1 |
Binding | High-level categorization of the type of activity in a care plan. For example codes, see CarePlanActivityCategory |
Type | CodeableConcept |
Requirements | May determine what types of extensions are permitted. |
48. CarePlan.activity.detail.definition | |
Definition | Identifies the protocol, questionnaire, guideline or other specification the planned activity should be conducted in accordance with. |
Control | 0..1 |
Type | Reference(ehealth-plandefinition | ehealth-activitydefinition | ehealth-questionnaire) |
Requirements | Allows Questionnaires that the patient (or practitioner) should fill in to fulfill the care plan activity. |
49. CarePlan.activity.detail.code | |
Definition | Detailed description of the type of planned activity; e.g. What lab test, what procedure, what kind of encounter. |
Control | 0..1 |
Binding | Detailed description of the type of activity; e.g. What lab test, what procedure, what kind of encounter. For example codes, see Care Plan Activity |
Type | CodeableConcept |
Requirements | Allows matching performed to planned as well as validation against protocols. |
Comments | Tends to be less relevant for activities involving particular products. Codes should not convey negation - use "prohibited" instead. |
50. CarePlan.activity.detail.reasonCode | |
Definition | Provides the rationale that drove the inclusion of this particular activity as part of the plan or the reason why the activity was prohibited. |
Control | 0..* |
Binding | Identifies why a care plan activity is needed. Can include any health condition codes as well as such concepts as "general wellness", prophylaxis, surgical preparation, etc. For example codes, see Activity Reason |
Type | CodeableConcept |
Comments | This could be a diagnosis code. If a full condition record exists or additional detail is needed, use reasonCondition instead. |
51. CarePlan.activity.detail.reasonReference | |
Definition | Provides the health condition(s) that drove the inclusion of this particular activity as part of the plan. |
Control | 0..* |
Type | Reference(ehealth-condition) |
Comments | Conditions can be identified at the activity level that are not identified as reasons for the overall plan. |
52. CarePlan.activity.detail.goal | |
Definition | Internal reference that identifies the goals that this activity is intended to contribute towards meeting. |
Control | 0..* |
Type | Reference(Goal) |
Requirements | So that participants know the link explicitly. |
53. CarePlan.activity.detail.status | |
Definition | Identifies what progress is being made for the specific activity. |
Control | 1..1 |
Binding | Indicates where the activity is at in its overall life cycle. The codes SHALL be taken from CarePlanActivityStatus |
Type | code |
Is Modifier | true |
Requirements | Indicates progress against the plan, whether the activity is still relevant for the plan. |
Comments | Some aspects of status can be inferred based on the resources linked in actionTaken. Note that "status" is only as current as the plan was most recently updated. |
54. CarePlan.activity.detail.statusReason | |
Definition | Provides reason why the activity isn't yet started, is on hold, was cancelled, etc. |
Control | 0..1 |
Type | string |
Comments | Will generally not be present if status is "complete". Be sure to prompt to update this (or at least remove the existing value) if the status is changed. |
55. CarePlan.activity.detail.prohibited | |
Definition | If true, indicates that the described activity is one that must NOT be engaged in when following the plan. If false, indicates that the described activity is one that should be engaged in when following the plan. |
Control | 0..1 |
Type | boolean |
Is Modifier | true |
Requirements | Captures intention to not do something that may have been previously typical. |
Comments | This element is labeled as a modifier because it marks an activity as an activity that is not to be performed. |
Default Value | false |
56. CarePlan.activity.detail.scheduled[x] | |
Definition | The period, timing or frequency upon which the described activity is to occur. |
Control | 0..1 |
Type | Choice of: Timing, Period, string |
[x] Note | See Choice of Data Types for further information about how to use [x] |
Requirements | Allows prompting for activities and detection of missed planned activities. |
57. CarePlan.activity.detail.location | |
Definition | Identifies the facility where the activity will occur; e.g. home, hospital, specific clinic, etc. |
Control | 0..1 |
Type | Reference(Location) |
Requirements | Helps in planning of activity. |
Comments | May reference a specific clinical location or may identify a type of location. |
58. CarePlan.activity.detail.performer | |
Definition | Identifies who's expected to be involved in the activity. |
Control | 0..* |
Type | Reference(ehealth-practitioner | ehealth-organization | ehealth-relatedperson | ehealth-patient | ehealth-careteam) |
Requirements | Helps in planning of activity. |
Comments | A performer MAY also be a participant in the care plan. |
59. CarePlan.activity.detail.product[x] | |
Definition | Identifies the food, drug or other product to be consumed or supplied in the activity. |
Control | 0..1 |
Binding | A product supplied or administered as part of a care plan activity. For example codes, see SNOMED CT Medication Codes |
Type | Choice of: CodeableConcept, Reference(Medication | Substance) |
[x] Note | See Choice of Data Types for further information about how to use [x] |
60. CarePlan.activity.detail.dailyAmount | |
Definition | Identifies the quantity expected to be consumed in a given day. |
Control | 0..1 |
Type | Quantity(SimpleQuantity) |
Requirements | Allows rough dose checking. |
Alternate Names | daily dose |
61. CarePlan.activity.detail.quantity | |
Definition | Identifies the quantity expected to be supplied, administered or consumed by the subject. |
Control | 0..1 |
Type | Quantity(SimpleQuantity) |
62. CarePlan.activity.detail.description | |
Definition | This provides a textual description of constraints on the intended activity occurrence, including relation to other activities. It may also include objectives, pre-conditions and end-conditions. Finally, it may convey specifics about the activity such as body site, method, route, etc. |
Control | 0..1 |
Type | string |
63. CarePlan.note | |
Definition | General notes about the care plan not covered elsewhere. |
Control | 0..* |
Type | Annotation |
Requirements | Used to capture information that applies to the plan as a whole that doesn't fit into discrete elements. |
64. CarePlan.note.id | |
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Control | 0..1 |
Type | string |
65. CarePlan.note.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. |
Control | 0..* |
Type | Extension |
Alternate Names | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Slicing | This element introduces a set of slices on CarePlan.note.extension. The slices are unordered and Open, and can be differentiated using the following discriminators:
|
66. CarePlan.note.author[x] | |
Definition | The individual responsible for making the annotation. |
Control | 0..1 |
Type | Choice of: Reference(ehealth-practitioner | ehealth-patient | ehealth-relatedperson), string |
[x] Note | See Choice of Data Types for further information about how to use [x] |
67. CarePlan.note.time | |
Definition | Indicates when this particular annotation was made. |
Control | 0..1 |
Type | dateTime |
68. CarePlan.note.text | |
Definition | The text of the annotation. |
Control | 1..1 |
Type | string |