Generated Narrative: StructureDefinition ACP-Medical-Policy-Goal Name Flags Card. Type Description & Constraints Goal 0..* Goal Describes the intended objective(s) for a patient, group or organization #xD; Slices for extension Content/Rules for all slices #xD; extension:encounter 0..1 (Complex) ext Encounter Reference URL: https://api.iknl.nl/docs/pzp/stu3/StructureDefinition/ext-EncounterReference #xD; value[x] 0..1 Reference(Encounter(1.0.0-rc1)) Encounter #xD; description 1..1 CodeableConcept Code or text describing goal Binding: MedicalPolicyGoalVS (1.0.0-rc1) (required) #xD; subject 0..1 Reference(Patient(1.0.0-rc1)) Who this goal is intended for #xD; Slices for start[x] 0..1 date, CodeableConcept When goal pursuit begins Slice: Unordered, Open by type:$this #xD; start[x]:startDate 0..1 date When goal pursuit begins #xD; note #xD; text 1..1 string The annotation - text content #xD; Documentation for this format
The primary, agreed-upon goal of a patient's medical treatment policy. Based on Goal resource.
Copyright and related rights waived via CC0, https://creativecommons.org/publicdomain/zero/1.0/. This does not apply to information from third parties, for example a medical terminology system. The implementer alone is responsible for identifying and obtaining any necessary licenses or authorizations to utilize third party IP in connection with the specification or otherwise.
Describes the intended objective(s) for a patient, group or organization
Describes the intended objective(s) for a patient, group or organization care, for example, weight loss, restoring an activity of daily living, obtaining herd immunity via immunization, meeting a process improvement objective, etc.
Goal can be achieving a particular change or merely maintaining a current state or even slowing a decline.
If the resource is contained in another resource, it SHALL NOT contain nested Resources
not(parent::f:contained and f:contained)
If the resource is contained in another resource, it SHALL NOT contain any narrative
If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated
contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
not(exists(f:contained/*/f:meta/f:versionId)) and not(exists(f:contained/*/f:meta/f:lastUpdated))
If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource
contained.where(('#'+id in %resource.descendants().reference).not()).empty()
not(exists(for $id in f:contained/*/@id return $id[not(ancestor::f:contained/parent::*/descendant::f:reference/@value=concat('#', $id))]))
Belangrijkste doel van behandeling (AlgemeneMeting)
MetingNaam voor Belangrijkste doel van behandeling
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 may not always be associated with version changes to the resource.
A set of rules under which this content was created
A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content.
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. This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation.
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).
Text summary of the resource, for human interpretation
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.
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 in formation 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.
An extension to link the Encounter during which the Consent, Goal or DeviceUseStatement was created or to which the creation is tightly associated.
All FHIR elements must have a @value or children
hasValue() | (children().count() > id.count())
Must have either extensions or value[x], not both
exists(f:extension)!=exists(f:*[starts-with(local-name(.), 'value')])
unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Extensions are always sliced by (at least) url
Source of the definition for the extension code - a logical name or a URL.
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 SHALL be a URI for the Structure Definition defining the extension.
The Encounter during which this resource was created or to which the creation is tightly associated.
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 (e.g. completing the administrative registration after the encounter).
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.
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.
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).
Need to allow connection to a wider workflow.
proposed | accepted | planned | in-progress | on-target | ahead-of-target | behind-target | sustaining | achieved | on-hold | cancelled | entered-in-error | rejected
Indicates whether the goal has been reached and is still considered relevant.
This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid.
Allows measuring outcome and whether goal needs to be further tracked.
Indicates whether the goal has been met and is still being targeted
.statusCode in-progress = active (classCode = OBJ) achieved = complete sustaining = active (classCode=OBJC) cancelled = aborted
E.g. Treatment, dietary, behavioral, etc.
Indicates a category the goal falls within.
high-priority | medium-priority | low-priority
Identifies the mutually agreed level of importance associated with reaching/sustaining the goal.
Extensions are available to track priorities as established by each participant (i.e. Priority from the patient's perspective, different practitioners' perspectives, family member's perspectives) The ordinal extension on Coding can be used to convey a numerically comparable ranking to priority. (Keep in mind that different coding systems may use a "low value=important".
The level of importance associated with a goal
Human-readable and/or coded description of a specific desired objective of care, such as "control blood pressure" or "negotiate an obstacle course" or "dance with child at wedding".
If no code is available, use CodeableConcept.text.
Without a description of what's trying to be achieved, element has no purpose.
Identifies the patient, group or organization for whom the goal is being established.
Subject is optional to support annonymized reporting.
The date or event after which the goal should begin being pursued.
Goals can be established prior to there being an intention to start pursuing them; e.g. Goals for post-surgical recovery established prior to surgery.
Codes describing events that can trigger the initiation of a goal
Allows the progress of the goal to be monitored against an observation or due date.
Goal.target.measure is required if Goal.target.detail is populated
(detail.exists() and measure.exists()) or detail.exists().not()
(exists(f:*[starts-with(local-name(.), 'detail')]) and exists(f:measure)) or not(exists(f:*[starts-with(local-name(.), 'detail')]))
Additional Content defined by implementations
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.
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.
The parameter whose value is being tracked
The parameter whose value is being tracked, e.g. body weight, blood pressure, or hemoglobin A1c level.
Codes to identify the value being tracked, e.g. body weight, blood pressure, or hemoglobin A1c level.
The target value 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.
Codes to identify the target value of the focus to be achieved to signify the fulfillment of the goal.
Indicates either the date or the duration after start by which the goal should be met.
Identifies when the goal should be evaluated.
Identifies when the current status. I.e. When initially created, when achieved, when cancelled, etc.
To see the date for past statuses, query history.
Captures the reason for the current status.
This will typically be captured for statuses such as rejected, on-hold or cancelled, but could be present for others.
Indicates whose goal this is - patient goal, practitioner goal, etc.
This is the individual reponsible for establishing the goal, not necessarily who recorded it. (For that, use the Provenance resource.).
The identified conditions and other health record elements that are intended to be addressed by the goal.
Allows specific goals to explicitly linked to the concerns they're dealing with - makes the goal more understandable.
May be used for progress notes, concerns or other related information that doesn't actually describe the goal itself.
There's a need to capture information about the goal that doesn't actually describe the goal.
.inboundRelationship[typeCode=SUBJ].source[classCode=OBS, moodCode=EVN, code="annotation"].value
Individual responsible for the annotation
The individual responsible for making the annotation.
Indicates when this particular annotation was made.
What result was achieved regarding the goal?
Identifies the change (or lack of change) at the point when the status of the goal is assessed.
Note that this should not duplicate the goal status.
Outcome tracking is a key aspect of care planning.
The result of the goal; e.g. "25% increase in shoulder mobility", "Anxiety reduced to moderate levels". "15 kg weight loss sustained over 6 months"
Details of what's changed (or not changed).
The goal outcome is independent of the outcome of the related activities. For example, if the Goal is to achieve a target body weight of 150 lb and a care plan activity is defined to diet, then the care plan’s activity outcome could be calories consumed whereas goal outcome is an observation for the actual body weight measured.