HL7 FHIR Implementation Guide: minimal Common Oncology Data Elements (mCODE), v0.9.1

HL7 FHIR Implementation Guide: minimal Common Oncology Data Elements (mCODE), v0.9.1 FHIR Profiles - Local Development build (v0.9.1). See the Directory of published versions

CarePlan

Definitions for obf-CarePlan.

1. CarePlan-argoprofile
Definition

Describes 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. The Care Plan tracks the progress of activities associated with the plan.

Control0..*
Alternate NamesCare Team
Max Length0
2. CarePlan-argoprofile.id
Definition

The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.

Control0..1
Typeid
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. Bundles always have an id, though it is usually a generated UUID.

Max Length0
3. CarePlan-argoprofile.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.

Control0..1
TypeMeta
Max Length0
4. CarePlan-argoprofile.meta.id
Definition

unique id for the element within a resource (for internal references).

Control0..1
Typeid
5. CarePlan-argoprofile.meta.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.

Control0..*
TypeExtension
Alternate Namesextensions, 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.

SlicingThis element introduces a set of slices on CarePlan.meta.extension. The slices are unordered and Open, and can be differentiated using the following discriminators:
  • value @ url
6. sourcesystem
SliceNamesourcesystem
Definition

FHIR: This provides a minimal amount of Provenance information that can be used to track or differentiate the source of information in the resource. The source may identify another FHIR server, document, message, database, etc. FHIM: Identifies the computer system that created the medical record. This optional field may also be used to indicate that the medical record was originally created by a different organization from the one that is currently storing or utilizing the record in that the assigning authority of the Id could be set to that originating organization. This property is optional, as some systems will assume that all records that it contains originated in that system, however it is anticipated that it will become increasingly commonplace for records from multiple systems and organizations will be comingled in order to provide a complete picture of the patient's health record.

Control0..1
TypeExtension(SourceSystem) (Extension Type: uri)
7. CarePlan-argoprofile.meta.versionId
Definition

The version specific identifier, as it appears in the version portion of the URL. This values changes when the resource is created, updated, or deleted.

Control0..1
Typeid
Comments

The server assigns this value, and ignores what the client specifies, except in the case that the server is imposing version integrity on updates/deletes.

8. CarePlan-argoprofile.meta.lastUpdated
Definition

When the resource last changed - e.g. when the version changed.

Control0..1
Typeinstant
Comments

This value is always populated except when the resource is first being created. The server / resource manager sets this value; what a client provides is irrelevant.

9. CarePlan-argoprofile.meta.profile
Definition

A list of profiles StructureDefinitions that this resource claims to conform to. The URL is a reference to StructureDefinition.url.

Control0..*
Typeuri
Comments

It is up to the server and/or other infrastructure of policy to determine whether/how these claims are verified and/or updated over time. The list of profile URLs is a set.

10. CarePlan-argoprofile.meta.security
Definition

Security labels applied to this resource. These tags connect specific resources to the overall security policy and infrastructure.

Control0..*
BindingSecurity Labels from the Healthcare Privacy and Security Classification System.
The codes SHALL be taken from All Security Labels; other codes may be used where these codes are not suitable
TypeCoding
Comments

The security labels can be updated without changing the stated version of the resource The list of security labels is a set. Uniqueness is based the system/code, and version and display are ignored.

11. CarePlan-argoprofile.meta.tag
Definition

Tags applied to this resource. Tags are intended to be used to identify and relate resources to process and workflow, and applications are not required to consider the tags when interpreting the meaning of a resource.

Control0..*
BindingCodes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones"
TypeCoding
Comments

The tags can be updated without changing the stated version of the resource. The list of tags is a set. Uniqueness is based the system/code, and version and display are ignored.

12. CarePlan-argoprofile.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.

Control0..1
Typeuri
Is Modifiertrue
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 as much as possible.

Max Length0
13. CarePlan-argoprofile.language
Definition

The base language in which the resource is written.

Control0..1
BindingA human language.
The codes SHALL be taken from http://tools.ietf.org/html/bcp47
Typecode
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).

Max Length0
14. CarePlan-argoprofile.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.

Control1..1 This element is affected by the following invariants: dom-1
TypeNarrative
Must Supporttrue
Alternate Namesnarrative, html, xhtml, display
Comments

Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative.

Max Length0
15. CarePlan-argoprofile.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.

Control0..*
TypeResource
Alternate Namesinline 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.

Max Length0
16. CarePlan-argoprofile.extension
Definition

May be used to represent additional information that is not part of the basic definition of the resource. 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.

Control1..*
TypeExtension
Alternate Namesextensions, 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.

Max Length0
SlicingThis element introduces a set of slices on CarePlan.extension. The slices are unordered and Open, and can be differentiated using the following discriminators:
  • value @ url
17. basedon
SliceNamebasedon
Definition

The proposal, order, or plan that is partly or wholly fulfilled by this item.

Control0..*
TypeExtension(BasedOn) (Extension Type: Reference(Basic | ReferralRequest | ProcedureRequest | MedicationRequest | CarePlan))
Max Length0
18. statementdatetime
SliceNamestatementdatetime
Definition

The point in time when the statement was created.

Control0..1
TypeExtension(StatementDateTime) (Extension Type: dateTime)
Max Length0
19. reasoncode
SliceNamereasoncode
Definition

The explanation or justification for the current item or action, as a code. Reason is a string or CodeableConcept in DSTU2 but in later versions only a CodeableConcept.

Control0..*
TypeExtension(ReasonCode) (Extension Type: CodeableConcept)
Max Length0
20. careplanreplaces
SliceNamecareplanreplaces
Definition

The Care Plan that was replaced by the current Care Plan.

Control0..*
TypeExtension(CarePlanReplaces) (Extension Type: Reference(CarePlan))
Max Length0
21. careplanpartof
SliceNamecareplanpartof
Definition

The Care Plan that this Care Plan is a portion of.

Control0..*
TypeExtension(CarePlanPartOf) (Extension Type: Reference(CarePlan))
Max Length0
22. requestintent
SliceNamerequestintent
Definition

Indicates the level of authority/intentionality associated with the request and where the request fits into the workflow chain.

Control1..1
TypeExtension(RequestIntent) (Extension Type: CodeableConcept)
Max Length0
23. title
SliceNametitle
Definition

A distinguishing word or group of words naming an item.

Control0..1
TypeExtension(Title) (Extension Type: string)
Max Length0
24. CarePlan-argoprofile.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.

Control0..*
TypeExtension
Is Modifiertrue
Alternate Namesextensions, 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.

Max Length0
25. CarePlan-argoprofile.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).

NoteThis is a business identifier, not a resource identifier (see discussion)
Control0..*
TypeIdentifier
Requirements

Need to allow connection to a wider workflow.

Max Length0
26. CarePlan-argoprofile.subject
Definition

Who care plan is for.

Control1..1
TypeReference(Patient)
Must Supporttrue
Requirements

Identifies the patient or group whose intended care is described by the plan.

Max Length0
27. CarePlan-argoprofile.status
Definition

Indicates whether the plan is currently being acted upon, represents future intentions or is now a historical record.

Control1..1
BindingThe codes SHALL be taken from CarePlanStatus
Typecode
Is Modifiertrue
Must Supporttrue
Requirements

Indicates whether the plan is currently being acted upon, represents future intentions or is now a historical record.

Max Length0
28. CarePlan-argoprofile.context
Definition

Identifies the context in which this particular CarePlan is defined.

Control0..1
TypeReference(Encounter | EpisodeOfCare)
Comments

Activities conducted as a result of the care plan may well occur as part of other encounters/episodes.

Max Length0
29. CarePlan-argoprofile.period
Definition

Indicates when the plan did (or is intended to) come into effect and end.

Control0..1
TypePeriod
Requirements

Allows tracking what plan(s) are in effect at a particular time.

Comments

Any activities scheduled as part of the plan should be constrained to the specified period.

Max Length0
30. CarePlan-argoprofile.author
Definition

Identifies the individual(s) or ogranization who is responsible for the content of the care plan.

Control0..1
TypeReference(Patient | Practitioner | RelatedPerson | Organization)
Comments

Collaborative care plans may have multiple authors.

Max Length0
31. CarePlan-argoprofile.modified
Definition

Identifies the most recent date on which the plan has been revised.

Control0..1
TypedateTime
Requirements

Indicates how current the plan is.

Max Length0
32. CarePlan-argoprofile.category
Definition

Type of plan.

Control1..*
BindingIdentifies what "kind" of plan this is to support differentiation between multiple co-existing plans; e.g. "Home health", "psychiatric", "asthma", "disease management", etc.
For example codes, see Care Plan Category
TypeCodeableConcept
Must Supporttrue
Requirements

Identifies what "kind" of plan this is to support differentiation between multiple co-existing plans; e.g. "Home health", "psychiatric", "asthma", "disease management", "wellness plan", etc.

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.

Max Length0
InvariantsDefined on this element
arg-1: Must have a category of 'careplan' and a code system 'http://argonaut.hl7.org' (: where(coding.system='http://argonaut.hl7.org' and coding.code='assess-plan').exists())
33. CarePlan-argoprofile.description
Definition

A description of the scope and nature of the plan.

Control0..1
Typestring
Requirements

Provides more detail than conveyed by category.

Max Length0
34. CarePlan-argoprofile.addresses
Definition

Identifies the conditions/problems/concerns/diagnoses/etc. whose management and/or mitigation are handled by this plan.

Control0..*
TypeReference(Condition)
Requirements

Links plan to the conditions it manages. Also scopes plans - multiple plans may exist addressing different concerns.

Max Length0
35. CarePlan-argoprofile.support
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.

Control0..*
TypeReference(Resource)
Requirements

Identifies barriers and other considerations associated with the care plan.

Comments

Use "concern" to identify specific conditions addressed by the care plan.

Max Length0
36. CarePlan-argoprofile.relatedPlan
Definition

Identifies CarePlans with some sort of formal relationship to the current plan.

Control0..*
TypeBackboneElement
Comments

Relationships are uni-directional with the "newer" plan pointing to the older one.

Max Length0
37. CarePlan-argoprofile.relatedPlan.id
Definition

unique id for the element within a resource (for internal references).

Control0..1
Typeid
Max Length0
38. CarePlan-argoprofile.relatedPlan.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.

Control0..*
TypeExtension
Alternate Namesextensions, 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.

Max Length0
39. CarePlan-argoprofile.relatedPlan.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.

Control0..*
TypeExtension
Is Modifiertrue
Alternate Namesextensions, 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.

Max Length0
40. CarePlan-argoprofile.relatedPlan.code
Definition

Identifies the type of relationship this plan has to the target plan.

Control0..1
BindingCodes identifying the types of relationships between two plans.
The codes SHALL be taken from CarePlanRelationship
Typecode
Comments

Read the relationship as "this plan" [relatedPlan.code] "relatedPlan.plan"; e.g. This plan includes Plan B. Additional relationship types can be proposed for future releases or handled as extensions.

Max Length0
41. CarePlan-argoprofile.relatedPlan.plan
Definition

A reference to the plan to which a relationship is asserted.

Control1..1
TypeReference(CarePlan)
Max Length0
42. CarePlan-argoprofile.participant
Definition

Identifies all people and organizations who are expected to be involved in the care envisioned by this plan.

Control0..*
TypeBackboneElement
Requirements

Allows representation of care teams, helps scope care plan. In some cases may be a determiner of access permissions.

Alternate NamesCare Team
Max Length0
43. CarePlan-argoprofile.participant.id
Definition

unique id for the element within a resource (for internal references).

Control0..1
Typeid
Max Length0
44. CarePlan-argoprofile.participant.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.

Control0..*
TypeExtension
Alternate Namesextensions, 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.

Max Length0
45. CarePlan-argoprofile.participant.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.

Control0..*
TypeExtension
Is Modifiertrue
Alternate Namesextensions, 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.

Max Length0
46. CarePlan-argoprofile.participant.role
Definition

Indicates specific responsibility of an individual within the care plan; e.g. "Primary physician", "Team coordinator", "Caregiver", etc.

Control0..1
BindingIndicates specific responsibility of an individual within the care plan; e.g. "Primary physician", "Team coordinator", "Caregiver", etc.
For example codes, see Participant Roles
TypeCodeableConcept
Comments

Roles may sometimes be inferred by type of Practitioner. These are relationships that hold only within the context of the care plan. General relationships should be handled as properties of the Patient resource directly.

Max Length0
47. CarePlan-argoprofile.participant.member
Definition

The specific person or organization who is participating/expected to participate in the care plan.

Control0..1
TypeReference(Practitioner | RelatedPerson | Patient | Organization)
Comments

Patient only needs to be listed if they have a role other than "subject of care". Member is optional because some participants may be known only by their role, particularly in draft plans.

Max Length0
48. CarePlan-argoprofile.goal
Definition

Describes the intended objective(s) of carrying out the care plan.

Control0..*
TypeReference(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.

Max Length0
49. CarePlan-argoprofile.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.

Control0..*
TypeBackboneElement
Requirements

Allows systems to prompt for performance of planned activities, and validate plans against best practice.

Max Length0
InvariantsDefined on this element
cpl-3: Provide a reference or detail, not both (: )
50. CarePlan-argoprofile.activity.id
Definition

unique id for the element within a resource (for internal references).

Control0..1
Typeid
Max Length0
51. CarePlan-argoprofile.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.

Control0..*
TypeExtension
Alternate Namesextensions, 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.

Max Length0
52. CarePlan-argoprofile.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.

Control0..*
TypeExtension
Is Modifiertrue
Alternate Namesextensions, 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.

Max Length0
53. CarePlan-argoprofile.activity.actionResulting
Definition

Resources that describe follow-on actions resulting from the plan, such as drug prescriptions, encounter records, appointments, etc.

Control0..*
TypeReference(Resource)
Requirements

Links plan to resulting actions.

Max Length0
54. CarePlan-argoprofile.activity.progress
Definition

Notes about the adherence/status/progress of the activity.

Control0..*
TypeAnnotation
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.

Max Length0
55. CarePlan-argoprofile.activity.reference
Definition

The details of the proposed activity represented in a specific resource.

Control0..1 This element is affected by the following invariants: cpl-3
TypeReference(Appointment | CommunicationRequest | DeviceUseRequest | DiagnosticOrder | MedicationOrder | NutritionOrder | Order | ProcedureRequest | ProcessRequest | ReferralRequest | SupplyRequest | VisionPrescription)
Requirements

Details in a form consistent with other applications and contexts of use.

Max Length0
56. CarePlan-argoprofile.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.

Control0..1 This element is affected by the following invariants: cpl-3
TypeBackboneElement
Requirements

Details in a simple form for generic care plan systems.

Max Length0
57. CarePlan-argoprofile.activity.detail.id
Definition

unique id for the element within a resource (for internal references).

Control0..1
Typeid
Max Length0
58. CarePlan-argoprofile.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.

Control0..*
TypeExtension
Alternate Namesextensions, 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.

Max Length0
59. CarePlan-argoprofile.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.

Control0..*
TypeExtension
Is Modifiertrue
Alternate Namesextensions, 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.

Max Length0
60. CarePlan-argoprofile.activity.detail.category
Definition

High-level categorization of the type of activity in a care plan.

Control0..1
BindingHigh-level categorization of the type of activity in a care plan.
For example codes, see CarePlanActivityCategory
TypeCodeableConcept
Requirements

May determine what types of extensions are permitted.

Max Length0
61. CarePlan-argoprofile.activity.detail.code
Definition

Detailed description of the type of planned activity; e.g. What lab test, what procedure, what kind of encounter.

Control0..1
BindingDetailed description of the type of activity; e.g. What lab test, what procedure, what kind of encounter.
For example codes, see Care Plan Activity
TypeCodeableConcept
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.

Max Length0
62. CarePlan-argoprofile.activity.detail.reasonCode
Definition

Provides the rationale that drove the inclusion of this particular activity as part of the plan.

Control0..*
BindingIdentifies 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
TypeCodeableConcept
Comments

This could be a diagnosis code. If a full condition record exists or additional detail is needed, use reasonCondition instead.

Max Length0
63. CarePlan-argoprofile.activity.detail.reasonReference
Definition

Provides the health condition(s) that drove the inclusion of this particular activity as part of the plan.

Control0..*
TypeReference(Condition)
Comments

Conditions can be identified at the activity level that are not identified as reasons for the overall plan.

Max Length0
64. CarePlan-argoprofile.activity.detail.goal
Definition

Internal reference that identifies the goals that this activity is intended to contribute towards meeting.

Control0..*
TypeReference(Goal)
Requirements

So that participants know the link explicitly.

Max Length0
65. CarePlan-argoprofile.activity.detail.status
Definition

Identifies what progress is being made for the specific activity.

Control0..1
BindingIndicates where the activity is at in its overall life cycle.
The codes SHALL be taken from CarePlanActivityStatus
Typecode
Is Modifiertrue
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.

Max Length0
66. CarePlan-argoprofile.activity.detail.statusReason
Definition

Provides reason why the activity isn't yet started, is on hold, was cancelled, etc.

Control0..1
BindingDescribes why the current activity has the status it does; e.g. "Recovering from injury" as a reason for non-started or on-hold, "Patient does not enjoy activity" as a reason for cancelling a planned activity.
For example codes, see GoalStatusReason
TypeCodeableConcept
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.

Max Length0
67. CarePlan-argoprofile.activity.detail.prohibited
Definition

If true, indicates that the described activity is one that must NOT be engaged in when following the plan.

Control1..1
Typeboolean
Is Modifiertrue
Requirements

Captures intention to not do something that may have been previously typical.

Max Length0
68. CarePlan-argoprofile.activity.detail.scheduledx
Definition

The period, timing or frequency upon which the described activity is to occur.

Control0..1
TypeChoice of: Timing, Period, string
[x] NoteSee Choice of Data Types for further information about how to use [x]
Requirements

Allows prompting for activities and detection of missed planned activities.

Max Length0
69. CarePlan-argoprofile.activity.detail.location
Definition

Identifies the facility where the activity will occur; e.g. home, hospital, specific clinic, etc.

Control0..1
TypeReference(Location)
Requirements

Helps in planning of activity.

Comments

May reference a specific clinical location or may identify a type of location.

Max Length0
70. CarePlan-argoprofile.activity.detail.performer
Definition

Identifies who's expected to be involved in the activity.

Control0..*
TypeReference(Practitioner | Organization | RelatedPerson | Patient)
Requirements

Helps in planning of activity.

Comments

A performer MAY also be a participant in the care plan.

Max Length0
71. CarePlan-argoprofile.activity.detail.productx
Definition

Identifies the food, drug or other product to be consumed or supplied in the activity.

Control0..1
BindingA product supplied or administered as part of a care plan activity.
For example codes, see SNOMED CT Medication Codes
TypeChoice of: CodeableConcept, Reference(Medication | Substance)
[x] NoteSee Choice of Data Types for further information about how to use [x]
Max Length0
72. CarePlan-argoprofile.activity.detail.dailyAmount
Definition

Identifies the quantity expected to be consumed in a given day.

Control0..1
TypeQuantity(SimpleQuantity)
Requirements

Allows rough dose checking.

Alternate Namesdaily dose
Max Length0
73. CarePlan-argoprofile.activity.detail.quantity
Definition

Identifies the quantity expected to be supplied, administered or consumed by the subject.

Control0..1
TypeQuantity(SimpleQuantity)
Max Length0
74. CarePlan-argoprofile.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.

Control0..1
Typestring
Max Length0
75. CarePlan-argoprofile.note
Definition

General notes about the care plan not covered elsewhere.

Control0..1
TypeAnnotation(Annotation)
Requirements

Used to capture information that applies to the plan as a whole that doesn't fit into discrete elements.

Max Length0