Surgical History

The Surgical History feature allows the user to record, update or view the detail of historical procedures performed on the patient.

athenaNet does not have the concept of a single list of all procedures performed on a patient. To collect all CPT codes associated with a patient, you need to pull the surgical history, all of the claims for that patient, and possibly the procedure orders.

Surgical history is always manually updated by a user in athenaNet or updated by an external data source, most commonly an interface or CCDA import. athenahealth doesn’t automatically convert procedures from claims into surgical history.

SURGICAL
The surgical history section again contains a list of checkbox questions, with an optional list of surgery dates.

  • 'DEFAULT' is the Y/N checkbox that indicates whether the patient had this surgery before. If 'DEFAULT' is Y, then the SURGERYDATE is an optional list of surgery dates. Even one surgery date should be submitted as a (singleton) list.
  • 'surgicalhistoryprocedureid' ties it to the practice-specific surgical history question and can be used to tie the same question across multiple forms.
  • 'procedurecode' is the CPT code of the procedure, if configured as such by the practice. text is the patient-friendly name of the surgical history question.
Was this information helpful? Yes | No Thank you for your feedback! What went wrong? Incomplete or incorrect information | Irrelevant Content | Others
Submit

Endpoints

Add surgical history data to patient's chart

POST
/v1/{practiceid}/chart/{patientid}/surgicalhistory
Record historical surgery information performed on a specific patient
Was this information helpful? Yes | No Thank you for your feedback! What went wrong? Incomplete or incorrect information | Irrelevant Content | Others
Submit
Try in Postman

Input Parameters

Expand all

❙ required

practiceid integer practiceid
patientid integer patientid
Content-Type string Content type of the payload

❙ Request Body

Expand all
PATIENTFACINGCALL boolean When 'true' is passed we will collect relevant data and store in our database.
THIRDPARTYUSERNAME string User name of the patient in the third party application.
departmentid integer The athenaNet department id.
procedures array A JSON array of procedures, mimicking <a href="https://developer.athenahealth.com/docs/read/chart/Surgical_History">the inputs</a> described in the PUT/POST call. It is good practice to use the POST call whenever adding new surgical history, however do take note that when calling PUT, any procedures without a procedureid in the PUT call will also add new history.
sectionnote string Any additional section notes

Output Parameters

Expand all
errormessage string If the operation failed, this will contain any error messages.
procedureids string Procedure IDs of newly created procedures in surgical history
success string Whether the operation was successful.
Example Code

Get patient's surgical history data

GET
/v1/{practiceid}/chart/{patientid}/surgicalhistory
Retrieve a list of historical surgeries performed on the specific patient
Was this information helpful? Yes | No Thank you for your feedback! What went wrong? Incomplete or incorrect information | Irrelevant Content | Others
Submit
Try in Postman

Input Parameters

Expand all

❙ required

practiceid integer practiceid
patientid integer patientid
departmentid integer The athenaNet department id.
THIRDPARTYUSERNAME string User name of the patient in the third party application.
PATIENTFACINGCALL boolean When 'true' is passed we will collect relevant data and store in our database.

Output Parameters

Expand all
notelastmodifiedby string Last username to modify the surgical history note
notelastmodifieddatetime string Last date and time the surgical history note was modified
procedures array List of performed procedures
sectionnote string Additional note for the entire surgical history section, if any
Example Code

Update patient's social history data

PUT
/v1/{practiceid}/chart/{patientid}/surgicalhistory
Modifies the historical surgery information for a specific patient
Was this information helpful? Yes | No Thank you for your feedback! What went wrong? Incomplete or incorrect information | Irrelevant Content | Others
Submit
Try in Postman

Input Parameters

Expand all

❙ required

practiceid integer practiceid
patientid integer patientid
Content-Type string Content type of the payload

❙ Request Body

Expand all
PATIENTFACINGCALL boolean When 'true' is passed we will collect relevant data and store in our database.
THIRDPARTYUSERNAME string User name of the patient in the third party application.
departmentid integer The athenaNet department id.
procedures array A JSON array of procedures, mimicking <a href="https://developer.athenahealth.com/docs/read/chart/Surgical_History">the inputs</a> described in the PUT/POST call. It is good practice to use the POST call whenever adding new surgical history, however do take note that when calling PUT, any procedures without a procedureid in the PUT call will also add new history.
sectionnote string Any additional section notes

Output Parameters

Expand all
errormessage string If the operation failed, this will contain any error messages.
procedureids string Procedure IDs of newly created procedures in surgical history
success string Whether the operation was successful.
Example Code