DiagnosticOrder Profile
This DiagnosticOrder 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 record of a request for a diagnostic investigation service to be performed, such as a lab test or scan.
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 DiagnosticOrder 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 DiagnosticOrder resource is derived from the ORDERS tables in athenaPractice and athenaFlow, and includes only those orders that are for diagnostic tests. 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 DiagnosticOrder, an application shall perform an HTTP GET, specifying the identifier of the resources being retrieved.
GET [base]/fhir/DiagnosticOrder/[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 DiagnosticOrder 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 DiagnosticOrder resources, an application shall perform an HTTP GET, specifying the query parameters associated with the resource.
GET [base]/fhir/DiagnosticOrder?{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 DiagnosticOrder 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 ) | |
| code (token ) | Code to indicate the item (test or panel) being ordered |
| encounter (reference ) | The encounter that this diagnostic order is associated with |
| encounter-or-historical (reference ) | |
| event-date (date ) | The date at which the event happened |
| event-date-fromnow (quantity ) | Like event-date except expressed as a positive or negative offset from the current time in units of time , e.g. event-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 ) | Identifiers assigned to this order |
| item-status (token ) | proposed | draft | planned | requested | received | accepted | in-progress | review | completed | cancelled | suspended | rejected | failed |
| orderer (reference ) | Who ordered the test |
| patient (reference ) | Who and/or what test is about |
| status (token ) | proposed | draft | planned | requested | received | accepted | in-progress | review | completed | cancelled | suspended | rejected | failed |
| subject (reference ) | Who and/or what test is about |
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. |
Other Operations
This Implementation guide defines 1 operation:
| $generate | Generate Document |
For more information about operations, including how they are invoked, see Operations .
Generate Document
Generate a CDA or other standards based document from resource data associated with the patient referenced by patient parameter below.
GET [base]/$generate?{operation-parameters}| In Parameters: | |||||
| Name | Cardinality | Type | Binding | Profile | Documentation |
| patient | 0..1 | reference | A reference to the patient for whom the document will be generated. The document will include data from this patient's record. Patient can be omitted when the patient for whom the document is being generated can be inferred from other parameters. | ||
| type | 0..1 | token | GEDocumentReferenceGenerationDocumentType (unknown) | The type of document to be generated. | |
| class | 0..1 | token | GEDocumentReferenceGenerationDocumentClass (unknown) | The document class to be generated. | |
| format | 0..* | token | GEDocumentReferenceGenerationDocumentFormat (unknown) | The format to be used when generating the document. | |
| contentType | 0..1 | token | MimeType (unknown) | The contentType of the document to be generated. | |
| author | 0..* | reference | The author of the document. Must be a legal reference to a Patient or Practitioner known to the current system. | ||
| authenticator | 0..1 | reference | The legal authenticator of the document. Must be a legal reference to a Patient or Practitioner known to the current system. | ||
| encounter | 0..1 | reference | The encounter associated with the document. Must be a legal reference to an Encounter known to the current system. | ||
| fromDate | 0..1 | date | Start date of the time period associated with the data elements. | ||
| toDate | 0..1 | date | End date of the time period associated with the data elements. | ||
| description | 0..1 | string | A description to include within the DocumentReference returned by this operation. | ||
| exclusions | 0..* | uri | URIs identifing resources to exclude from the document. | ||
| persist | 0..1 | boolean | If true, the generated document will be persisted. The default if not specified is false. | ||
| securityLabel | 0..* | token | Security tags to be associated with this docment. | ||
| excludedSections | 0..* | string | URIs identifing sections to exclude from the document. | ||
| excludedResources | 0..* | string | URIs identifing resources to exclude from the document. | ||
| raw | 0..1 | boolean | true | false | ||
| Out Parameters: | |||||
| Name | Cardinality | Type | Binding | Profile | Documentation |
| return | 1..1 | DocumentReference | Binary | A populated DocumentReference or Binary resource containing metadata about the document and the body of the document in the content attachment (when raw=false or is omitted), or just the body of the document (when raw=true). | ||
The $generate operation constructs a document from resource data available for the specified subject.
Profile Content
The official URL for this profile is:
http://hl7.org/fhir/StructureDefinition/diagnosticorder-profile
A request for a diagnostic service
| Name | Flags | Card. | Type | Description & Constraints | |
|---|---|---|---|---|---|
  DiagnosticOrder | 0..* | DiagnosticOrder | A request for a diagnostic service | ||
 meta | ∑ | 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 | ||
 diagnosticorder-performer | 0..1 | Reference (Reference) | Extension | ||
 url | 1..1 | uri | "http://hl7.org/fhir/StructureDefinition/diagnosticorder-performer" | ||
  valueReference | 1..1 | Reference (Reference) | Value of extension | ||
| modifierExtension | ?! | 0..* | Extension | Extensions that cannot be ignored | |
| subject | ∑ | 1..1 | Reference (Patient ) | Who and/or what test is about | |
| orderer | ∑ | 0..1 | Reference (Practitioner ) | Who ordered the test | |
 identifier | ∑ | 0..* | Identifier | Identifiers assigned to this order | |
| encounter | ∑ | 0..1 | Reference (Encounter ) | The encounter that this diagnostic order is associated with | |
| reason | 0..* | CodeableConcept | Explanation/Justification for test Binding: Condition/Problem/Diagnosis Codes (example ) | ||
| supportingInformation | 0..* | Reference (Condition ) | Additional clinical information Example: {"reference":"Reference(Observation|Condition|DocumentReference)"} | ||
| status | ?! S∑ | 0..1 | code | proposed | draft | planned | requested | received | accepted | in-progress | review | completed | cancelled | suspended | rejected | failed Binding: DiagnosticOrderStatus (required ) | |
| priority | S ∑ | 0..1 | code | routine | urgent | stat | asap Binding: DiagnosticOrderPriority (required ) | |
| event | 0..* | BackboneElement | A list of events of interest in the lifecycle | ||
| extension | 0..* | Extension | Additional Content defined by implementations | ||
| modifierExtension | ?! | 0..* | Extension | Extensions that cannot be ignored | |
| status | ∑ | 1..1 | code | proposed | draft | planned | requested | received | accepted | in-progress | review | completed | cancelled | suspended | rejected | failed Binding: DiagnosticOrderStatus (required ) | |
| description | ∑ | 0..1 | CodeableConcept | More information about the event and its context Binding: Diagnostic Order Event Codes (example ) | |
| dateTime | ∑ | 1..1 | dateTime | The date at which the event happened | |
| actor | 0..1 | Reference (Practitioner | Device ) | Who recorded or did this | ||
| item | 0..1 | BackboneElement | The items the orderer requested | ||
| extension | 0..* | Extension | Additional Content defined by implementations | ||
| modifierExtension | ?! | 0..* | Extension | Extensions that cannot be ignored | |
| code | ∑ | 1..1 | CodeableConcept | Code to indicate the item (test or panel) being ordered Binding: LOINC Diagnostic Order Codes (preferred ) | |
| status | S ∑ | 0..1 | code | proposed | draft | planned | requested | received | accepted | in-progress | review | completed | cancelled | suspended | rejected | failed Binding: DiagnosticOrderStatus (required ) | |
| event | ∑ | 0..* | BackboneElement | Events specific to this item | |
| note | 0..* | Annotation | Other notes and comments | ||
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 .
| DiagnosticOrder Profile | ||
| DiagnosticOrder | DiagnosticOrder-Profile | FHIR_DIAGNOSTICORDERVIEW |
| ├ id | ID | %ORDGROUPID% |
| ├ extension | performer | |
| ├ subject | PID | MakeReference("PERSON",%PID%,"Patient") |
| ├ orderer | AUTHBYUSRID | MakeReference("USR",%ORDERER%,"Practitioner") |
| ├ identifier | ORDERTYPE,ORDERNUM | MakeIdentifier("U",getSiteSystem("ORDERNUM"),%ORDERNUM%) |
| ├ encounter | SDID | MakeReference("DOCUMENT",%SDID%,"Encounter") |
| ├ reason | MakeTextConcept(%REFERRALREASON%) | |
| ├ supportingInformation | DXGROUP | MakeReferenceList("PROBLEM",%SPRID%,"Condition") |
| ├ status | STATUS | MapCode(%STATUS%,"DIAGNOSTICORDERSTATUS") |
| ├ priority | PRIORITY | MapCode(%PRIORITY%,"DIAGNOSTICORDERPRIORITY") |
| │ ├ dateTime | ORDERDATE | %ORDERDATE% |
| │ ├ code | CODE | MakeOrderCodeConcept(%CODE%, %DESCRIPTION%,%SYSTEM%) |
| │ └ status | ORDERSTATUS | MapCode(%STATUS%,"DIAGNOSTICORDERSTATUS") |
| └ note | CLINCOMMENTS | |