Condition Profile
This Condition 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, search, create and update capabilities of these products.
Overview
Access and view recorded conditions, problems, or diagnosis recognized by a clinician.
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 Condition 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.
The profile also defines the content that must be supplied to the API Server in response to requests to populate Condition resources. Fields which are marked as Mandatory in this profile are those that must be supplied to the API Server in content used to populate a resource.
Source
The Condition resource is derived from the Problem and HealthConcern tables in athenaPractice and athenaFlow. Specific detail can be found in the Mappings section below.
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 Condition, an application shall perform an HTTP GET, specifying the identifier of the resources being retrieved.
GET [base]/fhir/Condition/[id]{?_format=[json|xml]&_summary=[true|data]}
Read Operation Parameters
| Parameter | Description |
|---|---|
| [base] | Specifies the base URL of the FHIR Server, e.g., https://cpsapisandbox.virenceaz.com:9443/demoAPIServer |
| [id] | Specifies the identifier of the Condition 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 Code | Description |
|---|---|
| 200 OK | The requested resource was found and is contained within the body of the HTTP response. |
| 401 Unauthorized | Authorization 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 Found | The 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 Error | The 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 Condition resources, an application shall perform an HTTP GET, specifying the query parameters associated with the resource.
GET [base]/fhir/Condition?{search-parameters}{&_count=[max-results]&_format=[json|xml]&_summary=[true|text|data]}
Search Operation Parameters
| Parameter | Description |
|---|---|
| [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 Condition 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 ) | |
| abatement (date ) | |
| abatement-fromnow (quantity ) | Like abatement except expressed as a positive or negative offset from the current time in units of time , e.g. abatement-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. |
| asserter (reference ) | Person who asserts this condition |
| category (token ) | The category of the condition |
| clinicalstatus (token ) | The clinical status of the condition |
| code (token ) | Code for the condition |
| date-recorded (date ) | A date, when the Condition statement was documented |
| date-recorded-fromnow (quantity ) | Like date-recorded except expressed as a positive or negative offset from the current time in units of time , e.g. date-recorded-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. |
| encounter (reference ) | Encounter when condition first asserted |
| encounter-or-historical (reference ) | |
| identifier (token ) | A unique identifier of the condition record |
| onset (date ) | Date related onsets (dateTime and Period) |
| onset-fromnow (quantity ) | Like onset except expressed as a positive or negative offset from the current time in units of time , e.g. onset-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. |
| onset-info (string ) | Other onsets (boolean, age, range, string) |
| patient (reference ) | Who has the condition? |
Search Operation HTTP Response Codes
| Response Code | Description |
|---|---|
| 200 OK | The 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 Unauthorized | Authorization 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 Error | The 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. |
Create Operation
Create operations are executed as specified in the HL7 FHIR RESTful API implementation definition. To create a new Condition resource, an application must perform an HTTP POST, specifying the content of the resource in the body of the request.
POST [base]/fhir/Condition?{_format=[json|xml]}
Create Operation Parameters
| Parameter | Description |
|---|---|
| [_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. |
Create Operation HTTP Response Codes
| Response Code | Description |
|---|---|
| 201 Created | The resource was created at the location specified in the HTTP Location header. Note: Unsupported fields will be accepted in a request but will not be persisted to the database. Some fields may be mapped to database specific codes which closely but not perfectly match the input. See the HL7 FHIR specification for more detail on server permitted changes. |
| 400 Bad Request | The resource could not be parsed, or failed basic validation rules. The body of the HTTP response will contain an OperationOutcome resource that provide more detail about the reason for the failure. |
| 401 Unauthorized | Authorization 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. |
| 422 Unprocessable Entity | The proposed resource violated server business rules. For example, a required field may be missing or a field may contain a value that is not supported by the API Server. The body of the HTTP response will contain an OperationOutcome resource that provide more detail about the reason for the failure. |
| 500 Server Error | The 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. |
Update Operation
Update operations are executed as specified in the HL7 FHIR RESTful API implementation definition. To create a new Condition resource, an application must perform an HTTP PUT, specifying the content of the resource in the body of the request.
PUT [base]/fhir/Condition/[id]?{_format=[json|xml]}
Update Operation Parameters
| Parameter | Description |
|---|---|
| [_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. |
Update Operation HTTP Response Codes
| Response Code | Description |
|---|---|
| 200 OK | The resource was updated at the location specified in the HTTP Location header. Note: Unsupported fields will be accepted in a request but will not be persisted to the database. Some fields may be mapped to database specific codes which closely but not perfectly match the input. See the HL7 FHIR specification for more detail on server permitted changes. |
| 400 Bad Request | The resource could not be parsed, or failed basic validation rules. The body of the HTTP response will contain an OperationOutcome resource that provide more detail about the reason for the failure. |
| 401 Unauthorized | Authorization 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. |
| 422 Unprocessable Entity | The proposed resource violated server business rules. For example, a required field may be missing or a field may contain a value that is not supported by the API Server. The body of the HTTP response will contain an OperationOutcome resource that provide more detail about the reason for the failure. |
| 500 Server Error | The 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/condition-profile
Detailed information about conditions, problems or diagnoses
| Name | Flags | Card. | Type | Description & Constraints | |
|---|---|---|---|---|---|
  Condition | ∑ | 0..* | Condition | Detailed information about conditions, problems or diagnoses | |
 meta | S ∑ | 0..1 | Meta | Metadata about the resource | |
 implicitRules | ?! ∑ | 0..1 | uri | A set of rules under which this content was created | |
| language | 0..1 | code | Language of the resource content Binding: IETF BCP-47  (required ) | ||
| text | I | 0..1 | Narrative | Text summary of the resource, for human interpretation | |
| contained | 0..* | Resource | Contained, inline Resources | ||
 extension | 0..* | Extension | Additional Content defined by implementations | ||
| modifierExtension | ?! | 0..* | Extension | Extensions that cannot be ignored | |
 identifier | S ∑ | 0..1 | Identifier | External Ids for this condition | |
 patient | ∑ | 1..1 | Reference (Patient ) | Who has the condition? | |
| encounter | ∑ | 0..1 | Reference (Encounter ) | Encounter when condition first asserted | |
| asserter | ∑ | 0..1 | Reference (Practitioner ) | Person who asserts this condition | |
| dateRecorded | ∑ | 0..1 | date | When first entered | |
| code | ∑ | 1..1 | CodeableConcept | Identification of the condition, problem or diagnosis Binding: Condition/Problem/Diagnosis Codes (example ) | |
 extension | 0..* | Extension | Additional Content defined by implementations | ||
 coding | ∑ | Coding | Code defined by a terminology system Slice: Unordered, Closed, by system | ||
| coding | ∑ | 0..4 | Coding | Code defined by a terminology system | |
| coding | ∑ | 0..1 | Coding | Code defined by a terminology system | |
| extension | 0..* | Extension | Additional Content defined by implementations | ||
| system | ∑ | 1..1 | uri | Identity of the terminology system Fixed Value: http://snomed.info/sct | |
| version | ∑ | 0..1 | string | Version of the system - if relevant | |
| code | ∑ | 1..1 | code | Symbol in syntax defined by the system | |
| display | ∑ | 0..1 | string | Representation defined by the system | |
 userSelected | ∑ | 0..1 | boolean | If this coding was chosen directly by the user | |
| coding | ∑ | 0..1 | Coding | Code defined by a terminology system | |
| extension | 0..* | Extension | Additional Content defined by implementations | ||
| system | ∑ | 1..1 | uri | Identity of the terminology system Fixed Value: http://hl7.org/fhir/sid/icd-10-us | |
| version | ∑ | 0..1 | string | Version of the system - if relevant | |
| code | ∑ | 1..1 | code | Symbol in syntax defined by the system | |
| display | ∑ | 0..1 | string | Representation defined by the system | |
| userSelected | ∑ | 0..1 | boolean | If this coding was chosen directly by the user | |
| coding | ∑ | 0..1 | Coding | Code defined by a terminology system | |
| extension | 0..* | Extension | Additional Content defined by implementations | ||
| system | ∑ | 1..1 | uri | Identity of the terminology system Fixed Value: http://hl7.org/fhir/sid/icd-9-cm/diagnosis | |
| version | ∑ | 0..1 | string | Version of the system - if relevant | |
| code | ∑ | 1..1 | code | Symbol in syntax defined by the system | |
| display | ∑ | 0..1 | string | Representation defined by the system | |
| userSelected | ∑ | 0..1 | boolean | If this coding was chosen directly by the user | |
| coding | ∑ | 0..1 | Coding | Code defined by a terminology system | |
| extension | 0..* | Extension | Additional Content defined by implementations | ||
| system | ∑ | 1..1 | uri | Identity of the terminology system Fixed Value: http://www.gehealthcare.com/fhir/codes/MEL | |
| version | ∑ | 0..1 | string | Version of the system - if relevant | |
| code | ∑ | 1..1 | code | Symbol in syntax defined by the system | |
| display | ∑ | 0..1 | string | Representation defined by the system | |
| userSelected | ∑ | 0..1 | boolean | If this coding was chosen directly by the user | |
| text | ∑ | 0..1 | string | Plain text representation of the concept | |
| category | ∑ | 0..1 | CodeableConcept | complaint | symptom | finding | diagnosis Binding: Condition Category Codes (preferred ) | |
| clinicalStatus | ?! ∑ | 0..1 | code | active | relapse | remission | resolved Binding: Condition Clinical Status Codes (preferred ) | |
| verificationStatus | ?! ∑ | 1..1 | code | provisional | differential | confirmed | refuted | entered-in-error | unknown Binding: ConditionVerificationStatus (required ) | |
| severity | ∑ | 0..1 | CodeableConcept | Subjective severity of condition Binding: Condition/Diagnosis Severity (preferred ) | |
 onset[x] | ∑ | 0..1 | dateTime , string | Estimated or actual date, date-time, or age | |
| abatement[x] | ∑ | 0..1 | dateTime , string | If/when in resolution/remission | |
| stage | ∑ I | 0..1 | BackboneElement | Stage/grade, usually assessed formally con-1: Stage SHALL have summary or assessment | |
| extension | 0..* | Extension | Additional Content defined by implementations | ||
| modifierExtension | ?! | 0..* | Extension | Extensions that cannot be ignored | |
| summary | ∑ I | 0..1 | CodeableConcept | Simple summary (disease specific) Binding: Condition Stage (example ) | |
| assessment | ∑ I | 0..* | Reference (ClinicalImpression | DiagnosticReport | Observation ) | Formal record of assessment | |
| evidence | ∑ I | 0..* | BackboneElement | Supporting evidence con-2: evidence SHALL have code or details | |
| extension | 0..* | Extension | Additional Content defined by implementations | ||
| modifierExtension | ?! | 0..* | Extension | Extensions that cannot be ignored | |
| code | ∑ I | 0..1 | CodeableConcept | Manifestation/symptom Binding: Manifestation and Symptom Codes (example ) | |
| detail | ∑ I | 0..* | Reference (Resource ) | Supporting information found elsewhere | |
| bodySite | ∑ | 0..* | CodeableConcept | Anatomical location, if relevant Binding: SNOMED CT Body Structures (example ) | |
| notes | ∑ | 0..1 | string | Additional information about the Condition | |
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 the API Server Terms and Conditions.
| Condition Profile | ||
| Condition | Condition-Profile | FHIR_CONDITIONVIEW |
| ├ id | MakeId("PROBLEM",%PRID%) | |
| ├ identifier | External Problem Identifier | MakeIdentifier("U",getSiteSystem("ProblemId"),%EXTSPRID%) |
| ├ patient | MakeReference("PERSON",%PID%,"Patient") | |
| ├ encounter | MakeReference("DOCUMENT",%SDID%,"Encounter") | |
| ├ asserter | MakeReference("USR",%USRID%,"Practitioner") | |
| ├ dateRecorded | %DB_CREATE_DATE% | |
| │ ├ coding | Condition Code | |
| │ ├ coding | SNOMEDCODE | |
| │ │ └ code | %SNOMEDCODE% | |
| │ ├ coding | ICD10CODE | |
| │ │ └ code | %ICD10CODE% | |
| │ ├ coding | ICD9CODE | |
| │ │ └ code | %ICD9CODE% | |
| │ ├ coding | CODE | |
| │ │ └ code | %CODE% | |
| │ └ text | %DESCRIPTION% | |
| ├ category | MapConcept(%CATEGORY%,"CONDITIONCATEGORY") | |
| ├ clinicalStatus | ACTIVE OR STOPREASON | IsActiveOrMapCode(%STOPDATE%,"active",%STOPREASON%,"CLINICALSTATUS") |
| ├ verificationStatus | VSTOPREASON | MapCode(%VSTOPREASON%,"VERIFICATIONSTATUS") |
| ├ onset[x] | %ONSETDATE% | %APROXONSETDATE% | |
| ├ abatement[x] | STOPDATE | %STOPDATE% | %APROXSTOPDATE% |
| └ notes | ANNOTATE | %ANNOTATE% |