Document Type - Prescription
Document Type - Prescription requires a physician or staff member to take action by either approving or denying the prescription and then faxing the document back to the pharmacy or closing the document to the patient’s chart. This feature allows the user to retrieve, add or modify prescription document information of a specific patient or a specific prescription document. The Document Type - Prescription Changed Subscription feature will allow the user to retrieve any changes made to the prescriptions documents since the last time this request was run. The user will need to initiate subscription. For more information about subscriptions, please refer Changed Data Subscriptions.
Prescription
By default, prescription documents are created in an open status.
Prescription – Change: Requests from pharmacies to substitute prescribed drugs, e.g., a request to substitute an on-formulary medication of the same class.
Prescription – Clarification: Clarifying questions from pharmacies regarding prescriptions, e.g., correct dosage amounts or the original quantity provided on the prescription.
Prescription – New: Requests from pharmacies for new prescriptions. This document class should not be used for adding new orders to an existing encounter or order group. See Order Prescription for more details.
Prescription – Prior Authorization Request: Requests from pharmacies for further authorization, typically for insurance reasons.
Prescription – Renewal: Requests to refill previously prescribed medication. The words “refill,” “renewal,” or “renew” typically appear on these forms.
Note: Subclassification is necessary for this document class.
Prescription Document Reassignment
Prescription documents can be reassigned to any username configured for the practice (including non-person usernames like PRACTICE). The prescription document must be in REVIEW status to be reassigned. API users need to use the document assignment GET endpoint to retrieve the list of valid usernames the document could be reassigned to in the practice.
Document Assignment Options
Before a prescription document can be reassigned, the API user needs to retrieve the list of valid usernames the document could be reassigned to in the practice. The GET /documentassignment/{documentid} endpoint retrieves the current status of the document and the list of all the usernames available for reassignment.
Document Reassignment
API users can reassign a prescription document using the PUT /patients/{patientid}/documents/prescription/{prescriptionid} endpoint. After retrieving the desired username with the document assignment GET, the API user uses the assignedto field to reassign the document to the chosen username.
Note: The prescription document must be in REVIEW to be reassigned. The reassignment of a prescription document in any other status causes an error.
Endpoints
- Primary
- Subscription
Retrieves a list of prescription document information for a specific patient
Input Parameters
Expand all❙ required
Output Parameters
Expand allRetrieves a specific prescription document information for a specific patient
Input Parameters
Expand allOutput Parameters
Expand allModifies the information for a specific prescription document
Input Parameters
Expand all❙ Request Body
Expand allRetrieves a specific page from the specific prescription document of the patient
Input Parameters
Expand allOutput Parameters
Expand allRetrieves a list of all events that can be input for this subscription. Note: This endpoint may rely on specific settings to be enabled in athenaNet Production to function properly that are not required in other environments. Please see <a href="https://docs.athenahealth.com/api/resources/best-practices-and-troubles… Rollout of APIs</a> for more information if you are experiencing issues.
Input Parameters
Expand all❙ required
Subscribes for changed prescription events Note: This endpoint may rely on specific settings to be enabled in athenaNet Production to function properly that are not required in other environments. Please see <a href="https://docs.athenahealth.com/api/resources/best-practices-and-troubles… Rollout of APIs</a> for more information if you are experiencing issues.
Input Parameters
Expand all❙ Request Body
Expand allOutput Parameters
Expand allRetrieves list of events applicable for prescription Note: This endpoint may rely on specific settings to be enabled in athenaNet Production to function properly that are not required in other environments. Please see <a href="https://docs.athenahealth.com/api/resources/best-practices-and-troubles… Rollout of APIs</a> for more information if you are experiencing issues.
Input Parameters
Expand all❙ required
Retrieves list of records of modified prescription data Note: This endpoint may rely on specific settings to be enabled in athenaNet Production to function properly that are not required in other environments. Please see <a href="https://docs.athenahealth.com/api/resources/best-practices-and-troubles… Rollout of APIs</a> for more information if you are experiencing issues.
Input Parameters
Expand all❙ required
Output Parameters
Expand allDelete an specific event which is no longer required Note: This endpoint may rely on specific settings to be enabled in athenaNet Production to function properly that are not required in other environments. Please see <a href="https://docs.athenahealth.com/api/resources/best-practices-and-troubles… Rollout of APIs</a> for more information if you are experiencing issues.