Goal Profile

This Goal profile is part of the set of resource profiles supported by the API Server used with the athenaPractice 12.3 and athenaFlow 9.12 products. It further describes read and search capabilities of these products. Note: The create and update operations are NOT supported for this resource.

Overview

The Goal resource captures the intended health objective for a patient, group, or organization of care. These can include dietary, fitness, immunization, and process improvement goals.

Scope and Usage

This profile is used to define the content that will be returned by the API Server in response to requests to access Goal resources. All elements listed in the differential profile view are Supported, which means that the API Server is capable of supplying these fields from the product database when they have been populated via the product or its APIs.

Source

The Goal resource is derived from the Goal tables in athenaPractice and athenaFlow. Specific detail can be found in the Mappings section in the profile detail page.

Supported Operations

The operations supported by this resource are listed below.

Read Operation

Read operations are executed as specified in the HL7 FHIR RESTful API implementation definition. To read a Goal, an application shall perform an HTTP GET, specifying the identifier of the resources being retrieved.

GET [base]/fhir/Goal/[id]{?_format=[json|xml]&_summary=[true|data]}

Read Operation Parameters

ParameterDescription
[base]Specifies the base URL of the FHIR Server, e.g., https://cpsapisandbox.virenceaz.com:9443/demoAPIServer
[id]Specifies the identifier of the Goal resource to retrieve
[_format]Specifies the format of the output and may be xml or json. When present, the _format value overrides the value of the Accept header in the request.
[_summary]Filters the output to include only summary elements (_summary=true) or to omit the generated narrative (_summary=data). Note: If the generated html narrative for the resource is not going to be used by the call, using _summary=data provides slightly improved API response times.

Read Operation HTTP Response Codes

Response CodeDescription
200 OKThe requested resource was found and is contained within the body of the HTTP response.
401 UnauthorizedAuthorization is required for this request, and either the Authorization header is missing or the supplied user credentials in the Authorization header are not valid or have expired. The body of the HTTP response will contain an OperationOutcome resource that indicates that Authorization is required.
404 Not FoundThe requested resource does not exist. The body of the HTTP response will contain an OperationOutcome resource that indicates that the resource could not be found.
500 Server ErrorThe server may return other error codes to indicate other error conditions. The body of the HTTP response will contain an OperationOutcome resource that indicates the nature of the error.

Search Operation

Search operations are executed as specified in the HL7 FHIR RESTful API implementation definition. To search for Goal resources, an application shall perform an HTTP GET, specifying the query parameters associated with the resource.

GET [base]/fhir/Goal?{search-parameters}{&_count=[max-results]&_format=[json|xml]&_summary=[true|text|data]}

Search Operation Parameters

ParameterDescription
[base]Specifies the base URL of the FHIR Server, e.g., https://cpsapisandbox.virenceaz.com:9443/demoAPIServer
[_count]Specifies the maximum number of search results to return in a single query. Note: The count of results does not limit the number of additional resources returned via the _include parameter. No more than max-results Goal resources which match the search criteria will be returned. The API Server has default and maximum limits for the value that can be specified for this parameter. These limits may vary depending upon the client application vendors participation level in the AthenaHealth Partner program. Note: The API Server support the HL7 FHIR Paging capability.
[_format]Specifies the format of the output and may be xml or json. When present, the _format value overrides the value of the Accept header in the request.
[_summary]Filters the output to include only narrative elements (_summary=text), summary elements (_summary=true) or to omit the generated narrative (_summary=data). Note: If the generated html narrative for the resource is not going to be used by the call, using _summary=data provides improved API response times, especially when returning larger result sets.
_id (token )The ID of the resource
_lastUpdated (date )
_lastUpdated-fromnow (quantity )Like _lastUpdated except expressed as a positive or negative offset from the current time in units of time , e.g. _lastUpdated-fromnow=ge7||d for more than seven days in the future or =le-2||mo for less than two months in the past. The unit must be specified.
_security (token )
_tag (token )
category (token )E.g. Treatment, dietary, behavioral, etc.
date (date )
date-fromnow (quantity )Like date except expressed as a positive or negative offset from the current time in units of time , e.g. date-fromnow=ge7||d for more than seven days in the future or =le-2||mo for less than two months in the past. The unit must be specified.
identifier (token )External Ids for this goal
patient (reference )Who this goal is intended for
status (token )proposed | planned | accepted | rejected | in-progress | achieved | sustaining | on-hold | cancelled
subject (reference )Who this goal is intended for
targetdate (date )Reach goal on or before
targetdate-fromnow (quantity )Like targetdate except expressed as a positive or negative offset from the current time in units of time , e.g. targetdate-fromnow=ge7||d for more than seven days in the future or =le-2||mo for less than two months in the past. The unit must be specified.

Search Operation HTTP Response Codes

Response CodeDescription
200 OKThe query was performed and any results found are contained within the body of the HTTP response. Note: The search API will return 200 OK when the query itself is successful, regardless of whether or not any matching results were found.
401 UnauthorizedAuthorization is required for this request, and either the Authorization header is missing or the supplied user credentials in the Authorization header are not valid or have expired. The body of the HTTP response will contain an OperationOutcome resource that indicates that Authorization is required.
500 Server ErrorThe server may return other error codes to indicate other error conditions. The body of the HTTP response will contain an OperationOutcome resource that indicates the nature of the error.

Profile Content

The official URL for this profile is:

http://hl7.org/fhir/StructureDefinition/goal-profile

Describes the intended objective(s) for a patient, group or organization

Name Flags Card. Type Description & Constraints
.. Goal0..*Goal Describes the intended objective(s) for a patient, group or organization
... meta0..1Meta Metadata about the resource
... implicitRules?! 0..1uri A set of rules under which this content was created
... language0..1code Language of the resource content

Binding: IETF BCP-47 (required )
... textI0..1Narrative Text summary of the resource, for human interpretation
... contained0..*Resource Contained, inline Resources
... extension0..*Extension Additional Content defined by implementations
... modifierExtension?!0..*Extension Extensions that cannot be ignored
... identifier0..*Identifier External Ids for this goal
... subject0..1Reference (Patient | Group | Organization )Who this goal is intended for
... start[x]0..1date , CodeableConcept When goal pursuit begins

Binding: GoalStartEvent (example )
... target[x]0..1date , Duration Reach goal on or before
... category0..*CodeableConcept E.g. Treatment, dietary, behavioral, etc.

Binding: GoalCategory (example )
... description1..1string What's the desired outcome?
... status?! 1..1code proposed | planned | accepted | rejected | in-progress | achieved | sustaining | on-hold | cancelled

Binding: GoalStatus (required )
... statusDate0..1date When goal status took effect
... statusReason0..1CodeableConcept Reason for current status

Binding: GoalStatusReason (example )
... author0..1Reference (Patient | Practitioner | RelatedPerson )Who's responsible for creating Goal?
... priority0..1CodeableConcept high | medium |low

Binding: GoalPriority (preferred )
... addresses0..*Reference (Condition | Observation | MedicationStatement | NutritionOrder | ProcedureRequest | RiskAssessment )Issues addressed by this goal
... note0..*Annotation Comments about the goal
... outcome0..*BackboneElement What was end result of goal?
.... extension0..*Extension Additional Content defined by implementations
.... modifierExtension?!0..*Extension Extensions that cannot be ignored
.... result[x]0..1CodeableConcept , Reference (Observation )Code or observation that resulted from goal

Binding: (unbound) (example )


 

athenaPractice Mapping

The mappings in this section represent the how data stored within athenaPractice is served through the product's APIs. athenaPractice and athenaFlow share a common schema for patient clinical data and only one is shown when these are the same. Use of this information is subject to the API Server Terms and Conditions .

FamilyMemberHistory Profile
FamilyMemberHistoryFamilyMemberHistory-ProfileFHIR_FAMILYMEMBERHISTORYVIEW
 ├ idMakeId(%FAMILYHEALTHHISTORYID%)
 ├ identifierMakeIdentifier("U",getSiteSystem("FamilyMemberHistoryId"),%FAMILYHEALTHHISTORYID%)
 ├ patientMakeReference(null,%PID%,"Patient")
 ├ date%DB_UPDATED_DATE%
 ├ statusMapCode(%STATUS%,"FAMILYHISTORYSTATUS")
 ├ relationshipMakeConcept(%CODE%,"http://snomed.info/sct",%RELATION%)
 ├ genderMapCode(%GENDER%, "GENDER")
 └ noteMakeAnnotation(%FHXCOMMENTS%)
      │ ├ code%SNOMEDCODE%
      │ └ display%LONGDESCRIPTION%
     └ text%DESCRIPTION%

athenaFlow Mapping

The mappings in this section represent the how data stored within athenaFlow is served through the product's APIs. Use of this information is subject to the API Server Terms and Conditions .

FamilyMemberHistory Profile
FamilyMemberHistoryFamilyMemberHistory-ProfileFHIR_FAMILYMEMBERHISTORYVIEW
 ├ idMakeId(%FAMILYHEALTHHISTORYID%)
 ├ identifierMakeIdentifier("U",getSiteSystem("FamilyMemberHistoryId"),%FAMILYHEALTHHISTORYID%)
 ├ patientMakeReference(null,%PID%,"Patient")
 ├ date%DB_UPDATED_DATE%
 ├ statusMapCode(%STATUS%,"FAMILYHISTORYSTATUS")
 ├ relationshipMakeConcept(%CODE%,"http://snomed.info/sct",%RELATION%)
 ├ genderMapCode(%GENDER%, "GENDER")
 └ noteMakeAnnotation(%FHXCOMMENTS%)
      │ ├ code%SNOMEDCODE%
      │ └ display%LONGDESCRIPTION%
     └ text%DESCRIPTION%