MedicationOrder Profile

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

MedicationOrder

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 MedicationOrder 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 MedicationOrder resource is derived from the PRESCRIB 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 MedicationOrder, an application shall perform an HTTP GET, specifying the identifier of the resources being retrieved.

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

GET [base]/fhir/MedicationOrder?{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 MedicationOrder 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 )
datewritten (date )Return prescriptions written on this date
datewritten-fromnow (quantity )Like datewritten except expressed as a positive or negative offset from the current time in units of time , e.g. datewritten-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.
ddid (token )
encounter (reference )Return prescriptions with this encounter identifier
identifier (token )Return prescriptions with this external identifier
medication (reference )Return administrations of this medication reference
ndc (token )
patient (reference )The identity of a patient to list orders for
prescriber (reference )Who ordered the medication(s)
rxnorm (token )
status (token )Status of the prescription

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

Prescription of medication to for patient

Name Flags Card. Type Description & Constraints
.. MedicationOrder0..*MedicationOrder Prescription of medication to for 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
...medicationorder-ndc0..1CodeableConcept Extension
.... url1..1uri "http://hl7.org/fhir/StructureDefinition/medicationorder-ndc"
.... valueCodeableConcept1..1CodeableConcept Value of extension
...medicationorder-ddid0..1CodeableConcept Extension
.... url1..1uri "http://hl7.org/fhir/StructureDefinition/MedicationOrder-ddid"
.... valueCodeableConcept1..1CodeableConcept Value of extension
...medicationorder-rxnorm0..1CodeableConcept Extension
...medicationorder-dispenser0..1Reference (Reference)Extension
.... url1..1uri "http://hl7.org/fhir/StructureDefinition/MedicationOrder-dispenser"
.... valueReference1..1Reference (Reference)Value of extension
... extension0..1?? [UriType[http://hl7.org/fhir/StructureDefinition/MedicationOrder-dispenseInstructions]]Extensionhttp://hl7.org/fhir/StructureDefinition/MedicationOrder-dispenseInstructions
.... extension0..*Extension Additional Content defined by implementations
.... url1..1uri "http://hl7.org/fhir/StructureDefinition/MedicationOrder-dispenseInstructions"
.... valueString1..1string Value of extension
... modifierExtension?!0..*Extension Extensions that cannot be ignored
... identifier0..1Identifier External identifier
.... extension0..*Extension Additional Content defined by implementations
.... use?! 0..1code usual | official | temp | secondary (If known)

Binding: IdentifierUse (required )
.... type0..1CodeableConcept Description of identifier

Binding: Identifier Type Codes (extensible )
.... system1..1uri The namespace for the identifier

Example: http://www.acme.com/identifiers/patient or urn:ietf:rfc:3986 if the Identifier.value itself is a full uri
.... value1..1string The value that is unique

Example: 123456
.... period0..1Period Time period when id is/was valid for use
.... assigner0..1Reference (Organization )Organization that issued id (may be just text)
... dateWritten0..1dateTime When prescription was authorized
... status?! 1..1code active | on-hold | completed | entered-in-error | stopped | draft

Binding: MedicationOrderStatus (required )
... dateEnded0..1dateTime When prescription was stopped
... reasonEnded0..1CodeableConcept Why prescription was stopped

Binding: (unbound) (example )
... patient0..1Reference (Patient )Who prescription is for
... prescriber0..1Reference (Practitioner )Who ordered the medication(s)
... encounter0..1Reference (Encounter )Created during encounter/admission/stay
... reason[x]0..1CodeableConcept , Reference (Condition )Reason or indication for writing the prescription

Binding: Condition/Problem/Diagnosis Codes (example )
... note0..1string Information about the prescription
... medicationReference1..1Reference (Medication )Medication to be taken
... dosageInstruction0..*BackboneElement How medication should be taken
.... extension0..*Extension Additional Content defined by implementations
.... modifierExtension?!0..*Extension Extensions that cannot be ignored
.... text0..1string Dosage instructions expressed as text
.... additionalInstructions0..1CodeableConcept Supplemental instructions - e.g. "with meals"

Binding: (unbound) (example )
.... timing0..1Timing When medication should be administered
.... asNeeded[x]0..1boolean , CodeableConcept Take "as needed" (for x)

Binding: (unbound) (example )
.... site[x]0..1CodeableConcept , Reference (BodySite )Body site to administer to

Binding: SNOMED CT Anatomical Structure for Administration Site Codes (example )
.... route0..1CodeableConcept How drug should enter body

Binding: SNOMED CT Route Codes (example )
.... method0..1CodeableConcept Technique for administering medication

Binding: (unbound) (example )
.... dose[x]0..1Range , SimpleQuantity Amount of medication per dose
.... rate[x]0..1Ratio , Range Amount of medication per unit of time
.... maxDosePerPeriod0..1Ratio Upper limit on medication per unit of time
... dispenseRequest0..1BackboneElement Medication supply authorization
.... extension0..*Extension Additional Content defined by implementations
.... modifierExtension?!0..*Extension Extensions that cannot be ignored
.... medication[x]0..1CodeableConcept , Reference (Medication )Product to be supplied
.... validityPeriod0..1Period Time period supply is authorized for
.... numberOfRepeatsAllowed0..1positiveInt Number of refills authorized
.... quantityI0..1SimpleQuantity Amount of medication to supply per dispense

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

sqty-1: The comparator is not used on a SimpleQuantity
.... expectedSupplyDuration0..1Duration Number of days supply per dispense
... substitution0..1BackboneElement Any restrictions on medication substitution
.... extension0..*Extension Additional Content defined by implementations
.... modifierExtension?!0..*Extension Extensions that cannot be ignored
.... type1..1CodeableConcept generic | formulary +

Binding: ActSubstanceAdminSubstitutionCode (example )
.... reason0..1CodeableConcept Why should (not) substitution be made

Binding: SubstanceAdminSubstitutionReason (example )
... priorPrescription0..1Reference (MedicationOrder )An order/prescription that this supersedes


 

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 .

MedicationOrder Profile
MedicationOrderMedicationOrder-ProfileFHIR_PRESCRIBVIEW
 ├ id%PTID%
 ├ extensionndc
 ├ extensionddid
 ├ extensionrxnormMakeRxnormExtensionList(%RXNORM%,"http://www.nlm.nih.gov/research/umls/rxnorm",null)
 ├ extensiondispenser
 ├ extensiondispenseInstructions
  │ ├ valueStringComputeFillsForString(%REFILLS%)
  │ ├ systemgetSiteIdSystem("PRESCRIB")
  │ └ value%PRESCRIPTIONORDERNUMBER%
 ├ dateWritten%CLINICALDATE%
 ├ statusIsActiveOrMapCode(%STOPDATE%,"active",%STOPREASON%,"PRESCRIBSTATUS")
 ├ dateEnded%STOPDATE%
 ├ reasonEndedGetConcept(%STOPREASON%,"PRESCRIBSTATUS")
 ├ patientMakeReference("PATIENT",%PID%, "Patient")
 ├ prescriberMakeReference("USR",%PVID%,"Practitioner")
 ├ encounterMakeReference("DOCUMENT",%SDID%,"Encounter")
 ├ reason[x]MakeTextConcept(%ANNOTATE%)
 ├ note%COMMENTS%
 └ medicationReferenceMakeReference("MEDINFO",%DDID%,"Medication",%DESCRIPTION%)
   ├ text%INSTRUCTIONS%
   ├ numberOfRepeatsAllowedComputeFills(%REFILLS%)
   ├ quantity%QUANTITY%
   └ typeMapConcept(%DAW%,"MEDSUBSTITUTION")

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 .

MedicationOrder Profile
MedicationOrderMedicationOrder-ProfileFHIR_PRESCRIBVIEW
 ├ id%PTID%
 ├ extensionndc
 ├ extensionddid
 ├ extensionrxnormMakeRxnormExtensionList(%RXNORM%,"http://www.nlm.nih.gov/research/umls/rxnorm",null)
 ├ extensiondispenser
 ├ extensiondispenseInstructions
  │ ├ valueStringComputeFillsForString(%REFILLS%)
  │ ├ systemgetSiteIdSystem("PRESCRIB")
  │ └ value%PRESCRIPTIONORDERNUMBER%
 ├ dateWritten%CLINICALDATE%
 ├ statusIsActiveOrMapCode(%STOPDATE%,"active",%STOPREASON%,"PRESCRIBSTATUS")
 ├ dateEnded%STOPDATE%
 ├ reasonEndedGetConcept(%STOPREASON%,"PRESCRIBSTATUS")
 ├ patientMakeReference("PATIENT",%PID%, "Patient")
 ├ prescriberMakeReference("USR",%PVID%,"Practitioner")
 ├ encounterMakeReference("DOCUMENT",%SDID%,"Encounter")
 ├ reason[x]MakeTextConcept(%ANNOTATE%)
 ├ note%COMMENTS%
 └ medicationReferenceMakeReference("MEDINFO",%DDID%,"Medication",%DESCRIPTION%)
   ├ text%INSTRUCTIONS%
   ├ numberOfRepeatsAllowedComputeFills(%REFILLS%)
   ├ quantity%QUANTITY%
   └ typeMapConcept(%DAW%,"MEDSUBSTITUTION")