import { Annotation } from './Annotation.js';
import { CarePlan_Activity } from './CarePlan_Activity.js';
import { CareTeam } from './CareTeam.js';
import { CodeableConcept } from './CodeableConcept.js';
import { CodeableReference } from './CodeableReference.js';
import { Condition } from './Condition.js';
import { Device } from './Device.js';
import { Encounter } from './Encounter.js';
import { Extension } from './Extension.js';
import { FhirPrimitive } from './FhirPrimitive.js';
import { Goal } from './Goal.js';
import { Group } from './Group.js';
import { Identifier } from './Identifier.js';
import { Meta } from './Meta.js';
import { Narrative } from './Narrative.js';
import { NutritionOrder } from './NutritionOrder.js';
import { Organization } from './Organization.js';
import { Patient } from './Patient.js';
import { Period } from './Period.js';
import { Practitioner } from './Practitioner.js';
import { PractitionerRole } from './PractitionerRole.js';
import { Reference } from './Reference.js';
import { RelatedPerson } from './RelatedPerson.js';
import { RequestOrchestration } from './RequestOrchestration.js';
import { Resource } from './Resource.js';
import { ServiceRequest } from './ServiceRequest.js';
export interface CarePlan {
    /**
     * @description The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.
     * @comment Within the context of the FHIR RESTful interactions, the resource has an id except for cases like the create and conditional update. Otherwise, the use of the resouce id depends on the given use case.
     * @short Logical id of this artifact
     */
    id?: string;
    /**
     * @description 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.
     * @short Metadata about the resource
     */
    meta?: Meta;
    /**
     * @description 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.
     * @comment 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 andor 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 its narrative along with other profiles, value sets, etc.
     * @short A set of rules under which this content was created
     */
    implicitRules?: FhirPrimitive<string>;
    /**
     * @description The base language in which the resource is written.
     * @comment 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).
     * @short Language of the resource content
     */
    language?: FhirPrimitive<string>;
    /**
     * @description 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.
     * @comment Contained resources do not have a 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.
     * @short Text summary of the resource, for human interpretation
     */
    text?: Narrative;
    /**
     * @description These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, nor can they have their own independent transaction scope. This is allowed to be a Parameters resource if and only if it is referenced by a resource that provides contextmeaning.
     * @comment 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.
     * @short Contained, inline Resources
     */
    contained?: Resource[];
    /**
     * @description 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 managable, 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.
     * @comment 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.
     * @short Additional content defined by implementations
     */
    extension?: Extension[];
    /**
     * @description 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 andor the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, 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).
     * @comment 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.
     * @short Extensions that cannot be ignored
     */
    modifierExtension?: Extension[];
    /**
     * @description 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.
     * @comment This is a business identifier, not a resource identifier (see [discussion](resource.html#identifiers)).  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.
     * @short External Ids for this plan
     */
    identifier?: Identifier[];
    /**
     * @description The URL pointing to a FHIR-defined protocol, guideline, questionnaire or other definition that is adhered to in whole or in part by this CarePlan.
     * @short Instantiates FHIR protocol or definition
     */
    instantiatesCanonical?: FhirPrimitive<string>[];
    /**
     * @description The URL pointing to an externally maintained protocol, guideline, questionnaire or other definition that is adhered to in whole or in part by this CarePlan.
     * @comment This might be an HTML page, PDF, etc. or could just be a non-resolvable URI identifier.
     * @short Instantiates external protocol or definition
     */
    instantiatesUri?: FhirPrimitive<string>[];
    /**
     * @description A higher-level request resource (i.e. a plan, proposal or order) that is fulfilled in whole or in part by this care plan.
     * @short Fulfills plan, proposal or order
     */
    basedOn?: Reference<CarePlan | ServiceRequest | RequestOrchestration | NutritionOrder>[];
    /**
     * @description Completed or terminated care plan whose function is taken by this new care plan.
     * @comment 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.
     * @short CarePlan replaced by this CarePlan
     */
    replaces?: Reference<CarePlan>[];
    /**
     * @description A larger care plan of which this particular care plan is a component or step.
     * @comment 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.
     * @short Part of referenced CarePlan
     */
    partOf?: Reference<CarePlan>[];
    /**
     * @description Indicates whether the plan is currently being acted upon, represents future intentions or is now a historical record.
     * @comment 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.
     * @short draft | active | on-hold | revoked | completed | entered-in-error | unknown
     */
    status: FhirPrimitive<string>;
    /**
     * @description Indicates the level of authorityintentionality associated with the care plan and where the care plan fits into the workflow chain.
     * @comment This element is labeled as a modifier because the intent alters when and how the resource is actually applicable.
  This element is expected to be immutable. E.g. A "proposal" instance should never change to be a "plan" instance or "order" instance. Instead, a new instance 'basedOn' the prior instance should be created with the new 'intent' value.
     * @short proposal | plan | order | option | directive
     */
    intent: FhirPrimitive<string>;
    /**
     * @description 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.
     * @comment 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.addresses.
     * @short Type of plan
     */
    category?: CodeableConcept[];
    /**
     * @description Human-friendly name for the care plan.
     * @short Human-friendly name for the care plan
     */
    title?: FhirPrimitive<string>;
    /**
     * @description A description of the scope and nature of the plan.
     * @short Summary of nature of plan
     */
    description?: FhirPrimitive<string>;
    /**
     * @description Identifies the patient or group whose intended care is described by the plan.
     * @short Who the care plan is for
     */
    subject: Reference<Patient | Group>;
    /**
     * @description The Encounter during which this CarePlan was created or to which the creation of this record is tightly associated.
     * @comment 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.
     * @short The Encounter during which this CarePlan was created
     */
    encounter?: Reference<Encounter>;
    /**
     * @description Indicates when the plan did (or is intended to) come into effect and end.
     * @comment 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 encounterepisode or across multiple encountersepisodes (e.g. the longitudinal management of a chronic condition).
     * @short Time period plan covers
     */
    period?: Period;
    /**
     * @description Represents when this particular CarePlan record was created in the system, which is often a system-generated date.
     * @short Date record was first recorded
     */
    created?: FhirPrimitive<string>;
    /**
     * @description When populated, the custodian is responsible for the care plan. The care plan is attributed to the custodian.
     * @comment The custodian might or might not be a contributor.
     * @short Who is the designated responsible party
     */
    custodian?: Reference<Patient | Practitioner | PractitionerRole | Device | RelatedPerson | Organization | CareTeam>;
    /**
     * @description Identifies the individual(s), organization or device who provided the contents of the care plan.
     * @comment Collaborative care plans may have multiple contributors.
     * @short Who provided the content of the care plan
     */
    contributor?: Reference<Patient | Practitioner | PractitionerRole | Device | RelatedPerson | Organization | CareTeam>[];
    /**
     * @description Identifies all people and organizations who are expected to be involved in the care envisioned by this plan.
     * @short Who's involved in plan?
     */
    careTeam?: Reference<CareTeam>[];
    /**
     * @description Identifies the conditionsproblemsconcernsdiagnosesetc. whose management andor mitigation are handled by this plan.
     * @comment Use CarePlan.addresses.concept when a code sufficiently describes the concern (e.g. condition, problem, diagnosis, risk). Use CarePlan.addresses.reference when referencing a resource, which allows more information to be conveyed, such as onset date. CarePlan.addresses.concept and CarePlan.addresses.reference are not meant to be duplicative. For a single concern, either CarePlan.addresses.concept or CarePlan.addresses.reference can be used. CarePlan.addresses.concept may be a summary code, or CarePlan.addresses.reference may be used to reference a very precise definition of the concern using Condition. Both CarePlan.addresses.concept and CarePlan.addresses.reference can be used if they are describing different concerns for the care plan.
     * @short Health issues this plan addresses
     */
    addresses?: CodeableReference<Condition>[];
    /**
     * @description Identifies portions of the patient's record that specifically influenced the formation of the plan.  These might include comorbidities, recent procedures, limitations, recent assessments, etc.
     * @comment Use "concern" to identify specific conditions addressed by the care plan.  supportingInfo can be used to convey one or more Advance Directives or Medical Treatment Consent Directives by referencing Consent or any other request resource with intent = directive.
     * @short Information considered as part of plan
     */
    supportingInfo?: Reference<Resource>[];
    /**
     * @description Describes the intended objective(s) of carrying out the care plan.
     * @comment Goal can be achieving a particular change or merely maintaining a current state or even slowing a decline.
     * @short Desired outcome of plan
     */
    goal?: Reference<Goal>[];
    /**
     * @backbone Nested BackboneElement: activity [0..*]
     */
    activity?: CarePlan_Activity[];
    /**
     * @description General notes about the care plan not covered elsewhere.
     * @short Comments about the plan
     */
    note?: Annotation[];
    /**
     * @const Auto-injected fixed value: CarePlan
     */
    resourceType: "CarePlan";
}
//# sourceMappingURL=CarePlan.d.ts.map