Encounter Profile

This Encounter 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

This is the recorded interaction between a patient and a healthcare provider for the purpose of receiving healthcare services or a health assessment.

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 Encounter 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

Each physician interaction with a patient in athenaPractice or athenaFlow results in a chart document, thus the Encounter resource is derived from the DOCUMENT table 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 Encounter, an application shall perform an HTTP GET, specifying the identifier of the resources being retrieved.

GET [base]/fhir/Encounter/[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 Encounter 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 Encounter resources, an application shall perform an HTTP GET, specifying the query parameters associated with the resource.

GET [base]/fhir/Encounter?{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 Encounter 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 )
appointment (reference )The appointment that scheduled this encounter
condition (reference )Reason the encounter takes place (resource)
date (date )A date within the period the Encounter lasted
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 )Identifier(s) by which this encounter is known
indication (reference )Reason the encounter takes place (resource)
location (reference )Location the encounter takes place
patient (reference )The patient present at the encounter
reason (token )Reason the encounter takes place (code)
status (token )planned | arrived | in-progress | onleave | finished | cancelled

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/encounter-profile

An interaction during which services are provided to the patient

Name Flags Card. Type Description & Constraints
.. Encounter0..*Encounter An interaction during which services are provided to the patient
... 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..1?? [UriType[http://hl7.org/fhir/StructureDefinition/encounter-summary]]Extensionhttp://hl7.org/fhir/StructureDefinition/encounter-summary
.... extension0..*Extension Additional Content defined by implementations
.... url1..1uri "http://hl7.org/fhir/StructureDefinition/encounter-summary"
.... valueString1..1string Value of extension
... extension0..1?? [UriType[http://hl7.org/fhir/StructureDefinition/encounter-description]]Extensionhttp://hl7.org/fhir/StructureDefinition/encounter-description
.... extension0..*Extension Additional Content defined by implementations
.... url1..1uri "http://hl7.org/fhir/StructureDefinition/encounter-description"
.... valueString1..1string Value of extension
... extension0..1?? [UriType[http://hl7.org/fhir/StructureDefinition/encounter-authenticator]]Extensionhttp://hl7.org/fhir/StructureDefinition/encounter-authenticator
.... extension0..*Extension Additional Content defined by implementations
.... url1..1uri "http://hl7.org/fhir/StructureDefinition/encounter-authenticator"
.... valueReference1..1Reference (Practitioner )Value of extension
... modifierExtension?!0..*Extension Extensions that cannot be ignored
... identifierS 0..*Identifier Identifier(s) by which this encounter is known
... status?! S1..1code planned | arrived | in-progress | onleave | finished | cancelled

Binding: EncounterState (required )
... statusHistory0..*BackboneElement List of past encounter statuses
.... extension0..*Extension Additional Content defined by implementations
.... modifierExtension?!0..*Extension Extensions that cannot be ignored
.... status1..1code planned | arrived | in-progress | onleave | finished | cancelled

Binding: EncounterState (required )
.... period1..1Period The time that the episode was in the specified status
... classS 0..1code inpatient | outpatient | ambulatory | emergency +

Binding: EncounterClass (required )
... typeS 0..*CodeableConcept Specific type of encounter

Binding: EncounterType (example )
... priority0..1CodeableConcept Indicates the urgency of the encounter

Binding: Encounter Priority (example )
... patientS 0..1Reference (Patient )The patient present at the encounter
... episodeOfCare0..*Reference (EpisodeOfCare )Episode(s) of care that this encounter should be recorded against
... incomingReferral0..*Reference (ReferralRequest )The ReferralRequest that initiated this encounter
... participant0..*BackboneElement List of participants involved in the encounter
.... extension0..*Extension Additional Content defined by implementations
.... modifierExtension?!0..*Extension Extensions that cannot be ignored
.... type0..*CodeableConcept Role of participant in encounter

Binding: ParticipantType (extensible )
.... period0..1Period Period of time during the encounter participant was present
.... individual0..1Reference (Practitioner | RelatedPerson )Persons involved in the encounter other than the patient
... appointment0..1Reference (Appointment )The appointment that scheduled this encounter
... period0..1Period The start and end time of the encounter
... lengthI0..1Duration Quantity of time the encounter lasted (less time absent)

qty-3: If a code for the unit is present, the system SHALL also be present

drt-1: There SHALL be a code if there is a value and it SHALL be an expression of time. If system is present, it SHALL be UCUM.
... reason0..*CodeableConcept Reason the encounter takes place (code)

Binding: Encounter Reason Codes (example )
... indication0..*Reference (Condition | Procedure )Reason the encounter takes place (resource)
... hospitalization0..1BackboneElement Details about the admission to a healthcare service
.... extension0..*Extension Additional Content defined by implementations
.... modifierExtension?!0..*Extension Extensions that cannot be ignored
.... preAdmissionIdentifier0..1Identifier Pre-admission identifier
.... origin0..1Reference (Location )The location from which the patient came before admission
.... admitSource0..1CodeableConcept From where patient was admitted (physician referral, transfer)

Binding: AdmitSource (preferred )
.... admittingDiagnosis0..*Reference (Condition )The admitting diagnosis as reported by admitting practitioner
.... reAdmission0..1CodeableConcept The type of hospital re-admission that has occurred (if any). If the value is absent, then this is not identified as a readmission

Binding: (unbound) (example )
.... dietPreference0..*CodeableConcept Diet preferences reported by the patient

Binding: Diet (example )
.... specialCourtesy0..*CodeableConcept Special courtesies (VIP, board member)

Binding: SpecialCourtesy (preferred )
.... specialArrangement0..*CodeableConcept Wheelchair, translator, stretcher, etc.

Binding: SpecialArrangements (preferred )
.... destination0..1Reference (Location )Location to which the patient is discharged
.... dischargeDisposition0..1CodeableConcept Category or kind of location after discharge

Binding: DischargeDisposition (preferred )
.... dischargeDiagnosis0..*Reference (Condition )The final diagnosis given a patient before release from the hospital after all testing, surgery, and workup are complete
... location0..*BackboneElement List of locations where the patient has been
.... extension0..*Extension Additional Content defined by implementations
.... modifierExtension?!0..*Extension Extensions that cannot be ignored
.... location1..1Reference (Location )Location the encounter takes place
.... status0..1code planned | active | reserved | completed

Binding: EncounterLocationStatus (required )
.... period0..1Period Time period during which the patient was present at the location
... serviceProvider0..1Reference (Organization )The custodian organization of this Encounter record
... partOf0..1Reference (Encounter )Another Encounter this encounter is part of


 

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 .

Encounter Profile
EncounterEncounter-ProfileFHIR_ENCOUNTERVIEW
 ├ idMakeId(%ID%)
 ├ extensionSUMMARY
  │ └ valueString%SUMMARY%
 ├ extensionDESCRIPTION
  │ └ valueString%DESCRIPTION%
 ├ extensionAUNTHENTICATOR
  │ └ valueReferenceMakeReference("USR",%PUBUSER%,"Practitioner")
 ├ identifierMakeIdentifier("RI",getSiteSystem("EncounterId"),%VID%)
 ├ statusMapCode(%STATUS%,"ENCOUNTERSTATUS")
 ├ typeMakeConcept(%TYPE%,"http://hl7.org/fhir/ValueSet/encounter-type", %DESCRIPTION%)
 ├ priorityMapConcept(%PRIORITY%,"ENCOUNTERPRIORITY")
 ├ patientMakeReference("PATIENTPROFILE",%PID%,"Patient")
 ├ participantMakeEncounterParticipantList("USR",%PARTICIPANTS%,"Practitioner")
 ├ appointmentMakeReference("APPOINTMENTS",%APPTID%,"Appointment")
 ├ periodMakeEMRPeriod(%STARTDATE%)
 ├ reasonMakeTextConcept(%REASON%)
 └ indicationMakeReferenceList("PROBLEM",%PROBLEMID%,"Condition")
   └ locationMakeReference("LOCREG",%DOCLOCATIONID%,"Location")

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 .

Encounter Profile
EncounterEncounter-ProfileFHIR_ENCOUNTERVIEW
 ├ idMakeId(%ID%)
 ├ extensionSUMMARY
  │ └ valueString%SUMMARY%
 ├ extensionDESCRIPTION
  │ └ valueString%DESCRIPTION%
 ├ extensionAUNTHENTICATOR
  │ └ valueReferenceMakeReference("USR",%PUBUSER%,"Practitioner")
 ├ identifierMakeIdentifier("RI",getSiteSystem("EncounterId"),%VID%)
 ├ statusMapCode(%STATUS%,"ENCOUNTERSTATUS")
 ├ typeMakeConcept(%TYPE%,"http://hl7.org/fhir/ValueSet/encounter-type", %DESCRIPTION%)
 ├ priorityMapConcept(%PRIORITY%,"ENCOUNTERPRIORITY")
 ├ patientMakeReference("PERSON",%PID%,"Patient")
 ├ participantMakeEncounterParticipantList("USR",%PARTICIPANTS%,"Practitioner")
 ├ appointmentMakeReference("APPT",%APPTID%,"Appointment")
 ├ periodMakeEMRPeriod(%STARTDATE%)
 ├ reasonMakeTextConcept(%REASON%)
 └ indicationMakeReferenceList("PROBLEM",%PROBLEMID%,"Condition")
   └ locationMakeReference("LOCREG",%DOCLOCATIONID%,"Location")