This page is part of the FHIR Specification (v0.0.82: DSTU 1). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions
Definitions for the goal-qicore-qicore-goal Profile.
Goal(QICore-Goal) | |
Definition | Describes the intended objective(s) of patient care, for example, weight loss, restoring an activity of daily living, etc. |
Control | 1..1 |
Type | Goal |
Comments | Goal can be achieving a particular change or merely maintaining a current state or even slowing a decline. |
Goal.id | |
Definition | The logical id of the resource, as used in the url for the resoure. Once assigned, this value never changes. |
Control | 0..1 |
Type | id |
Comments | The only time that a resource does not have an id is when it is being submitted to the server using a create operation. Bundles always have an id, though it is usually a generated UUID. |
Goal.meta | |
Definition | The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content may not always be associated with version changes to the resource. |
Control | 0..1 |
Type | Meta |
Goal.implicitRules | |
Definition | A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. |
Control | 0..1 |
Type | uri |
Is Modifier | true |
Comments | Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element as much as possible. |
Goal.language | |
Definition | The base language in which the resource is written. |
Control | 0..1 |
Binding | A human language The codes SHALL be taken from http://tools.ietf.org/html/bcp47 |
Type | code |
Comments | Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute). |
Goal.text | |
Definition | A human-readable narrative that contains a summary of the resource, and may be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety. |
Control | 0..1 This element is affected by the following invariants: dom-1 |
Type | Narrative |
Alternate Names | narrative, html, xhtml, display |
Comments | Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. |
Goal.contained | |
Definition | These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope. |
Control | 0..* |
Type | Resource |
Alternate Names | inline resources, anonymous resources, contained resources |
Comments | This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. |
Goal.extension | |
Definition | An Extension |
Control | 0..* |
Type | Extension |
Slicing | This element introduces a set of slices. The slicing rules are:
|
Goal.extension (http://hl7.org/fhir/StructureDefinition/goal-category) | |
Definition | The type of goal, expressed as a code, for example, Goal: weight loss, [SNOMED CT: 289169006]. |
Control | 0..1 |
Type | Extension (Extension Type: CodeableConcept) |
Goal.extension (http://hl7.org/fhir/StructureDefinition/goal-target) | |
Definition | The element describing the target for the goal, allowing the progress of the goal to be monitored against an observation. |
Control | 0..* |
Type | Extension (Extension Type: Element) |
Goal.extension.id | |
Definition | unique id for the element within a resource (for internal references). |
Control | 0..1 |
Type | id |
Goal.extension.extension | |
Definition | An Extension |
Control | 0..* |
Type | Extension |
Slicing | This element introduces a set of slices. The slicing rules are:
|
Goal.extension.extension (http://hl7.org/fhir/StructureDefinition/goal-measure) | |
Definition | The parameter whose value is being tracked, e.g., body weight, blood pressure, or hemoglobin A1c level. |
Control | 1..1 |
Type | Extension (Extension Type: CodeableConcept) |
Goal.extension.extension (http://hl7.org/fhir/StructureDefinition/goal-detail) | |
Definition | The target value range of the focus to be achieved to signify the fulfillment of the goal, e.g., 150 pounds, 7.0%. Either the high or low or both values of the range can be specified. When a low value is missing, it indicates that the goal is achieved at any focus value at or below the high value. Similarly, if the high value is missing, it indicates that the goal is achieved at any focus value at or above the low value. |
Control | 1..1 |
Type | Extension (Extension Type: Choice of: Range, CodeableConcept) |
Goal.extension.url | |
Definition | Source of the definition for the extension code - a logical name or a URL. |
Control | 1..1 |
Type | uri |
Comments | The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition should be version specific. This will ideally be the URI for the Resource Profile defining the extension, with the code for the extension after a #. |
Goal.extension.value[x] | |
Definition | Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list). |
Control | 0..1 |
Type | * |
Goal.extension (http://hl7.org/fhir/StructureDefinition/goal-effectiveTime) | |
Definition | The effective time period for the goal, from the time the goal was created to the time goal was removed or revoked as an active goal. |
Control | 0..1 |
Type | Extension (Extension Type: Period) |
Goal.extension (http://hl7.org/fhir/StructureDefinition/goal-reasonRejected) | |
Definition | The reason the goal was not accepted. Applies only if the status of the goal is rejected. |
Control | 0..1 |
Type | Extension (Extension Type: CodeableConcept) |
Goal.modifierExtension | |
Definition | May be used to represent additional information that is not part of the basic definition of the resource, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. |
Control | 0..* |
Type | Extension |
Alternate Names | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Goal.identifier | |
Definition | This records identifiers associated with this care plan that are defined by business processed 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). |
Control | 0..* |
Type | Identifier |
Requirements | Need to allow connection to a wider workflow. |
Goal.patient | |
Definition | Identifies the patient/subject whose intended care is described by the plan. |
Control | 0..1 |
Type | Reference (QICore-Patient)) |
Must Support | true |
Requirements | Goals are associated with a patient. |
Goal.description | |
Definition | Human-readable description of a specific desired objective of care. |
Control | 1..1 |
Type | string |
Requirements | Without a description of what's trying to be achieved, element has no purpose. |
Goal.status | |
Definition | Indicates whether the goal has been reached and is still considered relevant. |
Control | 0..1 |
Binding | Indicates whether the goal has been met and is still being targeted The codes SHALL be taken from GoalStatus |
Type | code |
Is Modifier | true |
Must Support | true |
Requirements | Allows measuring outcome and whether goal needs to be further tracked. |
Goal.notes | |
Definition | Any comments related to the goal. |
Control | 0..1 |
Type | string |
Requirements | There's a need to capture information about the goal that doesn't actually describe the goal. |
Comments | May be used for progress notes, concerns or other related information that doesn't actually describe the goal itself. |
Goal.concern | |
Definition | The identified conditions that this goal relates to - the condition that caused it to be created, or that it is intended to address. |
Control | 0..* |
Type | Reference (QICore-Condition)) |
Must Support | true |
Requirements | Allows specific goals to explicitly linked to conditions - makes the goal more understandable. |