Left: | Argonaut CarePlan Profile (http://fhir.org/guides/argonaut/StructureDefinition/argo-careplan) |
Right: | US Core CarePlan Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-careplan) |
Error | StructureDefinition.url | Values for url differ: 'http://fhir.org/guides/argonaut/StructureDefinition/argo-careplan' vs 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-careplan' |
Information | StructureDefinition.name | Values for name differ: 'Argonaut CarePlan Profile' vs 'USCoreCarePlanProfile' |
Information | StructureDefinition.status | Values for status differ: 'draft' vs 'active' |
Information | StructureDefinition.date | Values for date differ: '2016-10-18T00:00:00+11:00' vs '2023-10-17' |
Information | StructureDefinition.publisher | Values for publisher differ: 'Argonaut Project' vs 'HL7 International / Cross-Group Projects' |
Information | StructureDefinition.jurisdiction | Added the item 'urn:iso:std:iso:3166#US' |
Warning | StructureDefinition.fhirVersion | Values for fhirVersion differ: '1.0.2' vs '4.0.1' |
Information | StructureDefinition.short | Values for short differ: 'Argonaut CarePlan Profile' vs 'Healthcare plan for patient or group' |
Information | StructureDefinition.definition | Values for definition differ: 'Healthcare plan for patient or group.' vs '\-' |
Information | CarePlan | StructureDefinition USCoreCarePlanProfile has added constraint that is not found in Argonaut CarePlan Profile and it is uncertain whether they are compatible (contained.contained.empty()) |
Information | CarePlan | StructureDefinition USCoreCarePlanProfile has added constraint that is not found in Argonaut CarePlan Profile and it is uncertain whether they are compatible (contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()) |
Information | CarePlan | StructureDefinition USCoreCarePlanProfile has added constraint that is not found in Argonaut CarePlan Profile and it is uncertain whether they are compatible (contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()) |
Information | CarePlan | StructureDefinition USCoreCarePlanProfile has added constraint that is not found in Argonaut CarePlan Profile and it is uncertain whether they are compatible (contained.meta.security.empty()) |
Information | CarePlan | StructureDefinition USCoreCarePlanProfile has added constraint that is not found in Argonaut CarePlan Profile and it is uncertain whether they are compatible (text.`div`.exists()) |
Information | StructureDefinition.comment | Values for comment differ: '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.' vs 'The only time that a resource does not have an id is when it is being submitted to the server using a create operation.' |
Information | StructureDefinition.definition | Values for definition differ: '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.' vs 'The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.' |
Information | StructureDefinition.definition | Values for definition differ: 'A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content.' vs 'A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc.' |
Information | StructureDefinition.comment | Values for comment differ: '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.' vs '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. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.' |
Information | StructureDefinition.comment | Values for comment differ: '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).' vs '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).' |
Information | StructureDefinition.definition | Values for definition differ: '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.' vs 'A human-readable narrative that contains a summary of the resource and can 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.' |
Information | StructureDefinition.comment | Values for comment differ: 'Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative.' vs '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 information is added later.' |
Information | CarePlan.text | Element minimum cardinalities differ: '1' vs '0' |
Information | StructureDefinition.short | Values for short differ: 'xml:id (or equivalent in JSON)' vs 'Unique id for inter-element referencing' |
Information | StructureDefinition.definition | Values for definition differ: 'unique id for the element within a resource (for internal references).' vs 'Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.' |
Information | StructureDefinition.short | Values for short differ: 'Additional Content defined by implementations' vs 'Additional content defined by implementations' |
Information | StructureDefinition.definition | Values for definition differ: '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.' vs 'May be used to represent additional information that is not part of the basic definition of the element. 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 can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.' |
Information | StructureDefinition.short | Values for short differ: 'generated | extensions | additional | empty' vs 'generated | additional' |
Information | StructureDefinition.definition | Values for definition differ: 'generated | additional.' vs 'The status of the narrative - whether it's entirely generated (from just the defined data or the extensions too), or whether a human authored it and it may contain additional data.' |
Information | StructureDefinition.comment | Values for comment differ: 'The contents of the html element are an XHTML fragment containing only the basic html formatting elements described in chapters 7-11 and 15 of the HTML 4.0 standard, <a> elements (either name or href), images and internally contained stylesheets. The XHTML content may not contain a head, a body, external stylesheet references, scripts, forms, base/link/xlink, frames, iframes and objects.' vs 'The contents of the html element are an XHTML fragment containing only the basic html formatting elements described in chapters 7-11 and 15 of the HTML 4.0 standard, <a> elements (either name or href), images and internally contained stylesheets. The XHTML content SHALL NOT contain a head, a body, external stylesheet references, scripts, forms, base/link/xlink, frames, iframes and objects.' |
Warning | CarePlan.text.div | Elements differ in definition for mustSupport: 'false' vs 'true' |
Information | StructureDefinition.comment | Values for comment differ: '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.' vs '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. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.' |
Information | StructureDefinition.short | Values for short differ: 'Additional Content defined by implementations' vs 'Additional content defined by implementations' |
Information | StructureDefinition.definition | Values for definition differ: '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.' vs 'May be used to represent additional information that is not part of the basic definition of the resource. 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 can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.' |
Information | StructureDefinition.definition | Values for definition differ: '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.' vs '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 and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).' |
Information | StructureDefinition.definition | Values for definition differ: '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).' vs 'Business identifiers assigned to this care plan by the performer or other systems which remain constant as the resource is updated and propagates from server to server.' |
Information | StructureDefinition.requirements | Values for requirements differ: 'Need to allow connection to a wider workflow.' vs 'Allows identification of the care plan as it is known by various participating systems and in a way that remains consistent across servers.' |
Information | StructureDefinition.short | Values for short differ: 'Who care plan is for' vs 'Who the care plan is for' |
Information | StructureDefinition.short | Values for short differ: 'proposed | draft | active | completed | cancelled' vs 'draft | active | on-hold | revoked | completed | entered-in-error | unknown' |
Error | CarePlan.status | Unable to resolve left value set http://hl7.org/fhir/ValueSet/care-plan-status at CarePlan.status |
Information | StructureDefinition.comment | Values for comment differ: 'Any activities scheduled as part of the plan should be constrained to the specified period.' vs '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).' |
Information | StructureDefinition.short | Values for short differ: 'Who is responsible for contents of the plan' vs 'Who is the designated responsible party' |
Information | StructureDefinition.definition | Values for definition differ: 'Identifies the individual(s) or ogranization who is responsible for the content of the care plan.' vs 'When populated, the author is responsible for the care plan. The care plan is attributed to the author.' |
Information | StructureDefinition.comment | Values for comment differ: 'Collaborative care plans may have multiple authors.' vs 'The author may also be a contributor. For example, an organization can be an author, but not listed as a contributor.' |
Information | CarePlan.author | Element maximum cardinalities differ: '2147483647' vs '1' |
Information | StructureDefinition.comment | Values for comment differ: '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.' vs 'There may be multiple axes of categorization and one plan may serve multiple purposes. In some cases, this may be redundant with references to CarePlan.concern.' |
Information | StructureDefinition.requirements | Values for requirements differ: 'Links plan to the conditions it manages. Also scopes plans - multiple plans may exist addressing different concerns.' vs '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.' |
Information | StructureDefinition.short | Values for short differ: 'xml:id (or equivalent in JSON)' vs 'Unique id for inter-element referencing' |
Information | StructureDefinition.definition | Values for definition differ: 'unique id for the element within a resource (for internal references).' vs 'Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.' |
Information | StructureDefinition.short | Values for short differ: 'Additional Content defined by implementations' vs 'Additional content defined by implementations' |
Information | StructureDefinition.definition | Values for definition differ: '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.' vs 'May be used to represent additional information that is not part of the basic definition of the element. 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 can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.' |
Information | StructureDefinition.short | Values for short differ: 'Extensions that cannot be ignored' vs 'Extensions that cannot be ignored even if unrecognized' |
Information | StructureDefinition.definition | Values for definition differ: '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.' vs '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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).' |
Information | StructureDefinition.short | Values for short differ: 'xml:id (or equivalent in JSON)' vs 'Unique id for inter-element referencing' |
Information | StructureDefinition.definition | Values for definition differ: 'unique id for the element within a resource (for internal references).' vs 'Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.' |
Information | StructureDefinition.short | Values for short differ: 'Additional Content defined by implementations' vs 'Additional content defined by implementations' |
Information | StructureDefinition.definition | Values for definition differ: '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.' vs 'May be used to represent additional information that is not part of the basic definition of the element. 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 can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.' |
Information | StructureDefinition.short | Values for short differ: 'Extensions that cannot be ignored' vs 'Extensions that cannot be ignored even if unrecognized' |
Information | StructureDefinition.definition | Values for definition differ: '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.' vs '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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).' |
Information | StructureDefinition.definition | Values for definition differ: 'Detailed description of the type of planned activity; e.g. What lab test, what procedure, what kind of encounter.' vs 'Detailed description of the type of planned activity; e.g. what lab test, what procedure, what kind of encounter.' |
Information | StructureDefinition.short | Values for short differ: 'Why activity should be done' vs 'Why activity should be done or why activity was prohibited' |
Information | StructureDefinition.definition | Values for definition differ: 'Provides the rationale that drove the inclusion of this particular activity as part of the plan.' vs 'Provides the rationale that drove the inclusion of this particular activity as part of the plan or the reason why the activity was prohibited.' |
Information | StructureDefinition.short | Values for short differ: 'Condition triggering need for activity' vs 'Why activity is needed' |
Information | StructureDefinition.definition | Values for definition differ: 'Provides the health condition(s) that drove the inclusion of this particular activity as part of the plan.' vs 'Indicates another resource, such as the health condition(s), whose existence justifies this request and drove the inclusion of this particular activity as part of the plan.' |
Information | StructureDefinition.short | Values for short differ: 'not-started | scheduled | in-progress | on-hold | completed | cancelled' vs 'not-started | scheduled | in-progress | on-hold | completed | cancelled | stopped | unknown | entered-in-error' |
Information | StructureDefinition.comment | Values for comment differ: '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.' vs '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. 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 activity.' |
Information | CarePlan.activity.detail.status | Element minimum cardinalities differ: '0' vs '1' |
Information | CarePlan.note | Element maximum cardinalities differ: '1' vs '2147483647' |
Name | Value | Comments | |
---|---|---|---|
abstract | false | ||
baseDefinition | http://hl7.org/fhir/StructureDefinition/CarePlan | ||
copyright | Used by permission of HL7 International, all rights reserved Creative Commons License |
| |
date | 2016-10-18T00:00:00+11:00 | 2023-10-17 |
|
description | This profile sets minimum expectations for the CarePlan resource to record, search, and fetch assessment and plan of treatment data associated with a patient to promote interoperability and adoption through common implementation. It identifies which core elements, extensions, vocabularies, and value sets **SHALL** be present and constrains the way the elements are used when using the profile. It provides the floor for standards development for specific use cases. |
| |
experimental | false |
| |
fhirVersion | 1.0.2 | 4.0.1 |
|
jurisdiction | |||
jurisdiction[0] | urn:iso:std:iso:3166#US |
| |
kind | resource | ||
name | Argonaut CarePlan Profile | USCoreCarePlanProfile |
|
publisher | Argonaut Project | HL7 International / Cross-Group Projects |
|
purpose | |||
status | draft | active |
|
title | US Core CarePlan Profile |
| |
type | CarePlan | ||
url | http://fhir.org/guides/argonaut/StructureDefinition/argo-careplan | http://hl7.org/fhir/us/core/StructureDefinition/us-core-careplan |
|
version | 7.0.0-ballot |
|
Name | L Flags | L Card. | L Type | L Description & Constraints | R Flags | R Card. | R Type | R Description & Constraints | Comments | ||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
CarePlan | 0..* | CarePlan | Argonaut CarePlan Profile | 0..* | CarePlan | Healthcare plan for patient or group |
| ||||||
id | Σ | 0..1 | id | Logical id of this artifact | Σ | 0..1 | id | Logical id of this artifact | |||||
meta | Σ | 0..1 | Meta | Metadata about the resource | Σ | 0..1 | Meta | Metadata about the resource | |||||
implicitRules | ?!Σ | 0..1 | uri | A set of rules under which this content was created | ?!Σ | 0..1 | uri | A set of rules under which this content was created | |||||
language | 0..1 | code | Language of the resource content Binding: ?? (required): A human language. | 0..1 | code | Language of the resource content Binding: ?? (preferred): A human language.
| |||||||
text | S | 1..1 | Narrative | Text summary of the resource, for human interpretation | S | 0..1 | Narrative | Text summary of the resource, for human interpretation |
| ||||
id | 0..1 | id | xml:id (or equivalent in JSON) | 0..1 | string | Unique id for inter-element referencing | |||||||
extension | 0..* | Extension | Additional Content defined by implementations | 0..* | Extension | Additional content defined by implementations Slice: Unordered, Open by value:url | |||||||
status | S | 1..1 | code | generated | extensions | additional | empty Binding: ?? (required) | S | 1..1 | code | generated | additional Binding: ?? (required): Constrained value set of narrative statuses. | |||||
div | C | 1..1 | xhtml | Limited xhtml content txt-2: The narrative SHALL have some non-whitespace content txt-1: The narrative SHALL contain only the basic html formatting elements described in chapters 7-11 (except section 4 of chapter 9) and 15 of the HTML 4.0 standard, <a> elements (either name or href), images and internally contained style attributes txt-3: The narrative SHALL contain only the basic html formatting attributes described in chapters 7-11 (except section 4 of chapter 9) and 15 of the HTML 4.0 standard, <a> elements (either name or href), images and internally contained style attributes | SC | 1..1 | xhtml | Limited xhtml content txt-1: The narrative SHALL contain only the basic html formatting elements and attributes described in chapters 7-11 (except section 4 of chapter 9) and 15 of the HTML 4.0 standard, <a> elements (either name or href), images and internally contained style attributes txt-2: The narrative SHALL have some non-whitespace content |
| ||||
contained | 0..* | Resource | Contained, inline Resources | 0..* | Resource | Contained, inline Resources | |||||||
extension | 0..* | Extension | Additional Content defined by implementations | 0..* | Extension | Additional content defined by implementations | |||||||
modifierExtension | ?! | 0..* | Extension | Extensions that cannot be ignored | ?! | 0..* | Extension | Extensions that cannot be ignored | |||||
identifier | Σ | 0..* | Identifier | External Ids for this plan | Σ | 0..* | Identifier | External Ids for this plan | |||||
subject | S | 1..1 | Reference(Argonaut Patient Profile) | Who care plan is for | SΣ | 1..1 | Reference(US Core Patient Profile S | Group) | Who the care plan is for | |||||
status | ?!S | 1..1 | code | proposed | draft | active | completed | cancelled Binding: ?? (required) | ?!SΣ | 1..1 | code | draft | active | on-hold | revoked | completed | entered-in-error | unknown Binding: ?? (required): Indicates whether the plan is currently being acted upon, represents future intentions or is now a historical record. |
| ||||
context | Σ | 0..1 | Reference(Encounter | EpisodeOfCare) | Created in context of |
| ||||||||
period | Σ | 0..1 | Period | Time period plan covers | Σ | 0..1 | Period | Time period plan covers | |||||
author | Σ | 0..* | Reference(Patient | Practitioner | RelatedPerson | Organization) | Who is responsible for contents of the plan | Σ | 0..1 | Reference(Patient | Practitioner | PractitionerRole | Device | RelatedPerson | Organization | CareTeam) | Who is the designated responsible party |
| ||||
modified | Σ | 0..1 | dateTime | When last updated |
| ||||||||
category | SC | 1..* | CodeableConcept | Type of plan Binding: ?? (example): Identifies what "kind" of plan this is to support differentiation between multiple co-existing plans; e.g. "Home health", "psychiatric", "asthma", "disease management", etc. arg-1: Must have a category of 'careplan' and a code system 'http://argonaut.hl7.org' | SΣ | 1..* | CodeableConcept | Type of plan Slice: Unordered, Open by pattern:$this Binding: ?? (example): Identifies what "kind" of plan this is to support differentiation between multiple co-existing plans; e.g. "Home health", "psychiatric", "asthma", "disease management", etc. | |||||
description | Σ | 0..1 | string | Summary of nature of plan | Σ | 0..1 | string | Summary of nature of plan | |||||
addresses | Σ | 0..* | Reference(Condition) | Health issues this plan addresses | Σ | 0..* | Reference(Condition) | Health issues this plan addresses | |||||
support | 0..* | Reference(Resource) | Information considered as part of plan |
| |||||||||
relatedPlan | 0..* | BackboneElement | Plans related to this one |
| |||||||||
participant | 0..* | BackboneElement | Who's involved in plan? |
| |||||||||
goal | 0..* | Reference(Goal) | Desired outcome of plan | 0..* | Reference(Goal) | Desired outcome of plan | |||||||
activity | C | 0..* | BackboneElement | Action to occur as part of plan cpl-3: Provide a reference or detail, not both | C | 0..* | BackboneElement | Action to occur as part of plan cpl-3: Provide a reference or detail, not both | |||||
id | 0..1 | id | xml:id (or equivalent in JSON) | 0..1 | string | Unique id for inter-element referencing | |||||||
extension | 0..* | Extension | Additional Content defined by implementations | 0..* | Extension | Additional content defined by implementations | |||||||
modifierExtension | ?! | 0..* | Extension | Extensions that cannot be ignored | ?!Σ | 0..* | Extension | Extensions that cannot be ignored even if unrecognized | |||||
actionResulting | 0..* | Reference(Resource) | Appointments, orders, etc. |
| |||||||||
progress | 0..* | Annotation | Comments about the activity status/progress | 0..* | Annotation | Comments about the activity status/progress | |||||||
reference | C | 0..1 | Reference(Appointment | CommunicationRequest | DeviceUseRequest | DiagnosticOrder | MedicationOrder | NutritionOrder | Order | ProcedureRequest | ProcessRequest | ReferralRequest | SupplyRequest | VisionPrescription) | Activity details defined in specific resource | C | 0..1 | Reference(Appointment | CommunicationRequest | DeviceRequest | MedicationRequest | NutritionOrder | Task | ServiceRequest | VisionPrescription | RequestGroup) | Activity details defined in specific resource | |||||
detail | C | 0..1 | BackboneElement | In-line definition of activity | C | 0..1 | BackboneElement | In-line definition of activity | |||||
id | 0..1 | id | xml:id (or equivalent in JSON) | 0..1 | string | Unique id for inter-element referencing | |||||||
extension | 0..* | Extension | Additional Content defined by implementations | 0..* | Extension | Additional content defined by implementations | |||||||
modifierExtension | ?! | 0..* | Extension | Extensions that cannot be ignored | ?!Σ | 0..* | Extension | Extensions that cannot be ignored even if unrecognized | |||||
category | 0..1 | CodeableConcept | diet | drug | encounter | observation | procedure | supply | other Binding: ?? (example): High-level categorization of the type of activity in a care plan. |
| |||||||||
code | 0..1 | CodeableConcept | Detail type of activity Binding: ?? (example): Detailed description of the type of activity; e.g. What lab test, what procedure, what kind of encounter. | 0..1 | CodeableConcept | Detail type of activity Binding: ?? (example): Detailed description of the type of activity; e.g. What lab test, what procedure, what kind of encounter. | |||||||
reasonCode | 0..* | CodeableConcept | Why activity should be done Binding: ?? (example): 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. | 0..* | CodeableConcept | Why activity should be done or why activity was prohibited Binding: ?? (example): 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. | |||||||
reasonReference | 0..* | Reference(Condition) | Condition triggering need for activity | 0..* | Reference(Condition | Observation | DiagnosticReport | DocumentReference) | Why activity is needed | |||||||
goal | 0..* | Reference(Goal) | Goals this activity relates to | 0..* | Reference(Goal) | Goals this activity relates to | |||||||
status | ?! | 0..1 | code | not-started | scheduled | in-progress | on-hold | completed | cancelled Binding: ?? (required): Indicates where the activity is at in its overall life cycle. | ?! | 1..1 | code | not-started | scheduled | in-progress | on-hold | completed | cancelled | stopped | unknown | entered-in-error Binding: ?? (required): Codes that reflect the current state of a care plan activity within its overall life cycle. |
| ||||
statusReason | 0..1 | CodeableConcept | Reason for current status Binding: ?? (example): Describes 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. | 0..1 | CodeableConcept | Reason for current status | |||||||
prohibited | ?! | 1..1 | boolean | Do NOT do |
| ||||||||
scheduled[x] | 0..1 | Timing, Period, string | When activity is to occur | 0..1 | Timing, Period, string | When activity is to occur | |||||||
location | 0..1 | Reference(Location) | Where it should happen | 0..1 | Reference(Location) | Where it should happen | |||||||
performer | 0..* | Reference(Practitioner | Organization | RelatedPerson | Patient) | Who will be responsible? | 0..* | Reference(Practitioner | PractitionerRole | Organization | RelatedPerson | Patient | CareTeam | HealthcareService | Device) | Who will be responsible? | |||||||
product[x] | 0..1 | CodeableConcept, Reference(Medication | Substance) | What is to be administered/supplied Binding: ?? (example): A product supplied or administered as part of a care plan activity. | 0..1 | CodeableConcept, Reference(Medication | Substance) | What is to be administered/supplied Binding: ?? (example): A product supplied or administered as part of a care plan activity. | |||||||
dailyAmount | 0..1 | Quantity | How to consume/day? | 0..1 | Quantity | How to consume/day? | |||||||
quantity | 0..1 | Quantity | How much to administer/supply/consume | 0..1 | Quantity | How much to administer/supply/consume | |||||||
description | 0..1 | string | Extra info describing activity to perform | 0..1 | string | Extra info describing activity to perform | |||||||
kind | 0..1 | code | Appointment | CommunicationRequest | DeviceRequest | MedicationRequest | NutritionOrder | Task | ServiceRequest | VisionPrescription Binding: ?? (required): Resource types defined as part of FHIR that can be represented as in-line definitions of a care plan activity. |
| |||||||||
instantiatesCanonical | 0..* | canonical(PlanDefinition | ActivityDefinition | Questionnaire | Measure | OperationDefinition) | Instantiates FHIR protocol or definition |
| |||||||||
instantiatesUri | 0..* | uri | Instantiates external protocol or definition |
| |||||||||
doNotPerform | ?! | 0..1 | boolean | If true, activity is prohibiting action |
| ||||||||
outcomeCodeableConcept | 0..* | CodeableConcept | Results of the activity Binding: ?? (example): Identifies the results of the activity. |
| |||||||||
outcomeReference | 0..* | Reference(Resource) | Appointment, Encounter, Procedure, etc. |
| |||||||||
note | 0..1 | Annotation | Comments about the plan | 0..* | Annotation | Comments about the plan |
| ||||||
instantiatesCanonical | Σ | 0..* | canonical(PlanDefinition | Questionnaire | Measure | ActivityDefinition | OperationDefinition) | Instantiates FHIR protocol or definition |
| ||||||||
instantiatesUri | Σ | 0..* | uri | Instantiates external protocol or definition |
| ||||||||
basedOn | Σ | 0..* | Reference(CarePlan) | Fulfills CarePlan |
| ||||||||
replaces | Σ | 0..* | Reference(CarePlan) | CarePlan replaced by this CarePlan |
| ||||||||
partOf | Σ | 0..* | Reference(CarePlan) | Part of referenced CarePlan |
| ||||||||
intent | ?!SΣ | 1..1 | code | proposal | plan | order | option Binding: ?? (required): Codes indicating the degree of authority/intentionality associated with a care plan |
| ||||||||
title | Σ | 0..1 | string | Human-friendly name for the care plan |
| ||||||||
encounter | Σ | 0..1 | Reference(Encounter) | Encounter created as part of |
| ||||||||
created | Σ | 0..1 | dateTime | Date record was first recorded |
| ||||||||
contributor | 0..* | Reference(Patient | Practitioner | PractitionerRole | Device | RelatedPerson | Organization | CareTeam) | Who provided the content of the care plan |
| |||||||||
careTeam | 0..* | Reference(CareTeam) | Who's involved in plan? |
| |||||||||
supportingInfo | 0..* | Reference(Resource) | Information considered as part of plan |
| |||||||||
Documentation for this format |