Identificadores externos para este recurso

Instancia o protocolo ou definição FHIR

Instancia protocolo externo ou definição

Cumpre o plano de cuidado

Plano de cuidado substituído por este plano de cuidado

Parte do plano de cuidado referenciado

draft | active | on-hold | revoked | completed | entered-in-error | unknown

proposal | plan | order | option

Tipo de plano de cuidado

Nome casual para o plano de cuidado

Resumo da natureza do plano de cuidado

Paciente cujo o plano de cuidado referencia

Atendimento no qual o plano de cuidado foi definido

O período de tempo que o plano de cuidado abrange

Data em que o registro foi gravado pela primeira vez

Quem é o responsável pela definição do plano de cuidado

Quem forneceu o conteúdo do plano de cuidados

Quem está envolvido no plano de cuidado

Problemas de saúde que este plano aborda

Informações consideradas como parte do plano de cuidado

Resultado desejado do plano de cuidado

Ação a ocorrer como parte do plano de cuidado

Resultados da atividade

Appointment, Encounter, Procedure, etc.

Comentários sobre o status/progresso da atividade

Detalhes da atividade definidos em recurso específico

Definição da atividade em conformidade

Appointment | CommunicationRequest | DeviceRequest | MedicationRequest | NutritionOrder | Task | ServiceRequest | VisionPrescription

Instancia o protocolo ou definição FHIR

Instancia protocolo externo ou definição

Tipo de atividade detalhada

Por que a atividade deve ser feita ou por que a atividade foi proibida

Por que a atividade é necessária

Objetivos com os quais esta atividade se relaciona

not-started | scheduled | in-progress | on-hold | completed | cancelled | stopped | unknown | entered-in-error

Motivo do status atual

Se for verdade, a atividade está proibindo a ação

Quando a atividade deve ocorrer

Onde a atividade deve ocorrer

Quem será responsável pela atividade

O que deve ser administrado/fornecido

Como consumir/dia?

Quanto administrar/fornecer/consumir

Informações extras descrevendo a atividade a ser realizada

Comentários sobre o plano de cuidados

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.

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.

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.

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).

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.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

Identificadores externos para este recurso

This is a business identifier, not a resource identifier (see discussion). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number.

Allows identification of the care plan as it is known by various participating systems and in a way that remains consistent across servers.

Instancia o protocolo ou definição FHIR

Instancia protocolo externo ou definição

This might be an HTML page, PDF, etc. or could just be a non-resolvable URI identifier.

Cumpre o plano de cuidado

Allows tracing of the care plan and tracking whether proposals/recommendations were acted upon.

Plano de cuidado substituído por este plano de cuidado

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.

Allows tracing the continuation of a therapy or administrative process instantiated through multiple care plans.

Parte do plano de cuidado referenciado

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.

draft | active | on-hold | revoked | completed | entered-in-error | unknown

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.

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

Allows clinicians to determine whether the plan is actionable or not.

proposal | plan | order | option

This element is labeled as a modifier because the intent alters when and how the resource is actually applicable.

Codes indicating the degree of authority/intentionality associated with a care plan.

Proposals/recommendations, plans and orders all use the same structure and can exist in the same fulfillment chain.

Tipo de plano de cuidado

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.

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

Used for filtering what plan(s) are retrieved and displayed to different types of users.

Nome casual para o plano de cuidado

Resumo da natureza do plano de cuidado

Provides more detail than conveyed by category.

Paciente cujo o plano de cuidado referencia

Atendimento no qual o plano de cuidado foi definido

This will typically be the encounter the event occurred within, but some activities may be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter. CarePlan activities conducted as a result of the care plan may well occur as part of other encounters.

O período de tempo que o plano de cuidado abrange

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).

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

Data em que o registro foi gravado pela primeira vez

Quem é o responsável pela definição do plano de cuidado

The author may also be a contributor. For example, an organization can be an author, but not listed as a contributor.

Quem forneceu o conteúdo do plano de cuidados

Collaborative care plans may have multiple contributors.

Quem está envolvido no plano de cuidado

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

Problemas de saúde que este plano aborda

When the diagnosis is related to an allergy or intolerance, the Condition and AllergyIntolerance resources can both be used. However, to be actionable for decision support, using Condition alone is not sufficient as the allergy or intolerance condition needs to be represented as an AllergyIntolerance.

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.

Informações consideradas como parte do plano de cuidado

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

Identifies barriers and other considerations associated with the care plan.

Resultado desejado do plano de cuidado

Goal can be achieving a particular change or merely maintaining a current state or even slowing a decline.

Provides context for plan. Allows plan effectiveness to be evaluated by clinicians.

Ação a ocorrer como parte do plano de cuidado

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

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).

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.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

Resultados da atividade

Note that this should not duplicate the activity status (e.g. completed or in progress).

Identifies the results of the activity.

Appointment, Encounter, Procedure, etc.

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 lbs 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.

Links plan to resulting actions.

Comentários sobre o status/progresso da atividade

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.

Can be used to capture information about adherence, progress, concerns, etc.

Detalhes da atividade definidos em recurso específico

Standard extension exists (resource-pertainsToGoal) that allows goals to be referenced from any of the referenced resources in CarePlan.activity.reference.
The goal should be visible when the resource referenced by CarePlan.activity.reference is viewed independently from the CarePlan. Requests that are pointed to by a CarePlan using this element should not point to this CarePlan using the "basedOn" element. i.e. Requests that are part of a CarePlan are not "based on" the CarePlan.

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

Definição da atividade em conformidade

Details in a simple form for generic care plan systems.

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).

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.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

Appointment | CommunicationRequest | DeviceRequest | MedicationRequest | NutritionOrder | Task | ServiceRequest | VisionPrescription

Resource types defined as part of FHIR that can be represented as in-line definitions of a care plan activity.

May determine what types of extensions are permitted.

Instancia o protocolo ou definição FHIR

Allows Questionnaires that the patient (or practitioner) should fill in to fulfill the care plan activity.

Instancia protocolo externo ou definição

This might be an HTML page, PDF, etc. or could just be a non-resolvable URI identifier.

Allows Questionnaires that the patient (or practitioner) should fill in to fulfill the care plan activity.

Tipo de atividade detalhada

Tends to be less relevant for activities involving particular products. Codes should not convey negation - use "prohibited" instead.

Allows matching performed to planned as well as validation against protocols.

Por que a atividade deve ser feita ou por que a atividade foi proibida

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

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.

Por que a atividade é necessária

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

Objetivos com os quais esta atividade se relaciona

So that participants know the link explicitly.

not-started | scheduled | in-progress | on-hold | completed | cancelled | stopped | unknown | entered-in-error

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.

Codes that reflect the current state of a care plan activity within its overall life cycle.

Indicates progress against the plan, whether the activity is still relevant for the plan.

Motivo do status atual

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.

Se for verdade, a atividade está proibindo a ação

This element is labeled as a modifier because it marks an activity as an activity that is not to be performed.

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

Quando a atividade deve ocorrer

Allows prompting for activities and detection of missed planned activities.

Onde a atividade deve ocorrer

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

Helps in planning of activity.

Quem será responsável pela atividade

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

Helps in planning of activity.

O que deve ser administrado/fornecido

A product supplied or administered as part of a care plan activity.

Como consumir/dia?

Allows rough dose checking.

Quanto administrar/fornecer/consumir

Informações extras descrevendo a atividade a ser realizada

Comentários sobre o plano de cuidados

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

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.

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

The only time that a resource does not have an id is when it is being submitted to the server using a create operation.

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.

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.

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.

The base language in which the resource is written.

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).

A human language.

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.

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.

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.

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.

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.

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.

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).

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.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

Identificadores externos para este recurso

This is a business identifier, not a resource identifier (see discussion). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number.

Allows identification of the care plan as it is known by various participating systems and in a way that remains consistent across servers.

Instancia o protocolo ou definição FHIR

Instancia protocolo externo ou definição

This might be an HTML page, PDF, etc. or could just be a non-resolvable URI identifier.

Cumpre o plano de cuidado

Allows tracing of the care plan and tracking whether proposals/recommendations were acted upon.

Plano de cuidado substituído por este plano de cuidado

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.

Allows tracing the continuation of a therapy or administrative process instantiated through multiple care plans.

Parte do plano de cuidado referenciado

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.

draft | active | on-hold | revoked | completed | entered-in-error | unknown

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.

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

Allows clinicians to determine whether the plan is actionable or not.

proposal | plan | order | option

This element is labeled as a modifier because the intent alters when and how the resource is actually applicable.

Codes indicating the degree of authority/intentionality associated with a care plan.

Proposals/recommendations, plans and orders all use the same structure and can exist in the same fulfillment chain.

Tipo de plano de cuidado

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.

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

Used for filtering what plan(s) are retrieved and displayed to different types of users.

Nome casual para o plano de cuidado

Resumo da natureza do plano de cuidado

Provides more detail than conveyed by category.

Paciente cujo o plano de cuidado referencia

Atendimento no qual o plano de cuidado foi definido

This will typically be the encounter the event occurred within, but some activities may be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter. CarePlan activities conducted as a result of the care plan may well occur as part of other encounters.

O período de tempo que o plano de cuidado abrange

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).

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

Data em que o registro foi gravado pela primeira vez

Quem é o responsável pela definição do plano de cuidado

The author may also be a contributor. For example, an organization can be an author, but not listed as a contributor.

Quem forneceu o conteúdo do plano de cuidados

Collaborative care plans may have multiple contributors.

Quem está envolvido no plano de cuidado

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

Problemas de saúde que este plano aborda

When the diagnosis is related to an allergy or intolerance, the Condition and AllergyIntolerance resources can both be used. However, to be actionable for decision support, using Condition alone is not sufficient as the allergy or intolerance condition needs to be represented as an AllergyIntolerance.

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.

Informações consideradas como parte do plano de cuidado

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

Identifies barriers and other considerations associated with the care plan.

Resultado desejado do plano de cuidado

Goal can be achieving a particular change or merely maintaining a current state or even slowing a decline.

Provides context for plan. Allows plan effectiveness to be evaluated by clinicians.

Ação a ocorrer como parte do plano de cuidado

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

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

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.

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.

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).

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.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

Resultados da atividade

Note that this should not duplicate the activity status (e.g. completed or in progress).

Identifies the results of the activity.

Appointment, Encounter, Procedure, etc.

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 lbs 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.

Links plan to resulting actions.

Comentários sobre o status/progresso da atividade

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.

Can be used to capture information about adherence, progress, concerns, etc.

Detalhes da atividade definidos em recurso específico

Standard extension exists (resource-pertainsToGoal) that allows goals to be referenced from any of the referenced resources in CarePlan.activity.reference.
The goal should be visible when the resource referenced by CarePlan.activity.reference is viewed independently from the CarePlan. Requests that are pointed to by a CarePlan using this element should not point to this CarePlan using the "basedOn" element. i.e. Requests that are part of a CarePlan are not "based on" the CarePlan.

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

Definição da atividade em conformidade

Details in a simple form for generic care plan systems.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

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.

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.

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).

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.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

Appointment | CommunicationRequest | DeviceRequest | MedicationRequest | NutritionOrder | Task | ServiceRequest | VisionPrescription

Resource types defined as part of FHIR that can be represented as in-line definitions of a care plan activity.

May determine what types of extensions are permitted.

Instancia o protocolo ou definição FHIR

Allows Questionnaires that the patient (or practitioner) should fill in to fulfill the care plan activity.

Instancia protocolo externo ou definição

This might be an HTML page, PDF, etc. or could just be a non-resolvable URI identifier.

Allows Questionnaires that the patient (or practitioner) should fill in to fulfill the care plan activity.

Tipo de atividade detalhada

Tends to be less relevant for activities involving particular products. Codes should not convey negation - use "prohibited" instead.

Allows matching performed to planned as well as validation against protocols.

Por que a atividade deve ser feita ou por que a atividade foi proibida

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

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.

Por que a atividade é necessária

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

Objetivos com os quais esta atividade se relaciona

So that participants know the link explicitly.

not-started | scheduled | in-progress | on-hold | completed | cancelled | stopped | unknown | entered-in-error

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.

Codes that reflect the current state of a care plan activity within its overall life cycle.

Indicates progress against the plan, whether the activity is still relevant for the plan.

Motivo do status atual

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.

Se for verdade, a atividade está proibindo a ação

This element is labeled as a modifier because it marks an activity as an activity that is not to be performed.

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

Quando a atividade deve ocorrer

Allows prompting for activities and detection of missed planned activities.

Onde a atividade deve ocorrer

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

Helps in planning of activity.

Quem será responsável pela atividade

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

Helps in planning of activity.

O que deve ser administrado/fornecido

A product supplied or administered as part of a care plan activity.

Como consumir/dia?

Allows rough dose checking.

Quanto administrar/fornecer/consumir

Informações extras descrevendo a atividade a ser realizada

Comentários sobre o plano de cuidados

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