Example Usage Scenarios:

The following are example usage scenarios for this profile:

• Query for a Patient's Goals
• Record or update a Patient's Goals

Mandatory and Must Support Data Elements

The following data elements must always be present (Mandatory definition) or must be supported if the data is present in the sending system (Must Support definition). They are presented below in a simple human-readable explanation. Profile specific guidance and examples are provided as well. The Formal Views below provides the formal summary, definitions, and terminology requirements.

Each Goal Must Have:

1. a status
2. description of the goal*
3. a patient

Each Goal Must Support:

1. start date*
2. target date(s)*
3. who established the goal*

*see guidance below

Profile Specific Implementation Guidance:

• *Although both Goal.startDate and Goal.target.dueDate are marked as Must Support, the Server system is not required to support both, but SHALL support at least one of these elements. The Client application SHALL support both elements.
• *Goals are often captured as text and communicated in Goal.description.text. When the goal is a Social Determinants of Health (SDOH) goal, use the preferred Social Determinants of Health Goals binding.
• See the Screening and Assessments guidance page for more information when exchanging Social Determinants of Health (SDOH) Goals

• *The profile element Goal.expressedBy communicates the individual level provenance author data corresponding to the U.S. Core Data for Interoperability (USCDI) Provenance Author Data Elements.

Changes since version 7.0.0:

Quick Start

Below is an overview of the required Server RESTful FHIR interactions for this profile - for example, search and read operations - when supporting the US Core interactions to access this profile's information (Profile Support + Interaction Support). Note that systems that support only US Core Profiles (Profile Only Support) are not required to support these interactions. See the US Core Server CapabilityStatement for a complete list of supported RESTful interactions for this IG.

• See the Scopes Format section for a description of the SMART scopes syntax.
• See the Search Syntax section for a description of the US Core search syntax.
• See the General Requirements section for additional rules and expectations when a Server requires status parameters.
• See the General Guidance section for additional guidance on searching for multiple patients.

US Core Scopes

Servers providing access to goal data SHALL support these US Core SMART Scopes:

• resource level scopes: <patient|user|system>/Goal.rs

Mandatory Search Parameters:

The following search parameters and search parameter combinations SHALL be supported:

1. SHALL support searching for all goals for a patient using the patient search parameter:

   GET [base]/Goal?patient={Type/}[id]

   Example:

   1. GET [base]/Goal?patient=1137192

   Implementation Notes: Fetches a bundle of all Goal resources for the specified patient (how to search by reference)

Optional Search Parameters:

The following search parameter combinations SHOULD be supported:

1. SHOULD support searching using the combination of the patient and lifecycle-status search parameters:

   GET [base]/Goal?patient={Type/}[id]&lifecycle-status={system|}[code]

   Example:

   1. GET [base]/Goal?patient=1137192&lifecycle-status=active

   Implementation Notes: Fetches a bundle of all Goal resources for the specified patient and lifecycle-status (how to search by reference and how to search by token)

2. SHOULD support searching using the combination of the patient and target-date search parameters:
   • including support for these target-date comparators: gt,lt,ge,le
   • including optional support for AND search on target-date (e.g.target-date=[date]&target-date=[date]]&...)

   GET [base]/Goal?patient={Type/}[id]&target-date={gt|lt|ge|le}[date]{&target-date={gt|lt|ge|le}[date]&...}

   Example:

   1. GET [base]/Goal?patient=1137192&target-date=ge2015-01-14&target-date=le2019-01-14

   Implementation Notes: Fetches a bundle of all Goal resources for the specified patient and target-date (how to search by reference and how to search by date)

3. SHOULD support searching using the combination of the patient and description search parameters:

   GET [base]/Goal?patient={Type/}[id]&description={system|}[code]

   Example:

   1. GET [base]/Goal?patient=1137192&description=http://snomed.info/sct|1078229009

   Implementation Notes: Fetches a bundle of all Goal resources for the specified patient and description (how to search by reference and how to search by token)