V3 Change Log
Note: dates are based on when the change was made, which will generally be a week before the change reaches production.
From v2
- Scopes that provide access to information covered by user permissions on the web interface now respect those permissions.
- Insurances endpoint now properly checks for the
userscope - Verbose flag on all endpoints will return a paginated response with smaller page sizes
2016-09-06
- Added
primary_insurance/photo_front,primary_insurance/photo_back,secondary_insurance/photo_front,secondary_insurance/photo_back,tertiary_insurace/photo_front,tertiary_insurace/photo_backto/api/patients
2016-09-13
- Removed global daily rate limit. Hourly limit still in effect.
2016-11-01
- Made
custom_demographicsendpoint writable
2016-11-03
- In the
api/appointmentsendpoint, added thesinceparameter to the required filtering parameters
2016-11-17
- Added `/api/patients/:id/qrda1 to return QRDA-1 XML for the patient
2016-11-18
- Added
message_notesfield to/api/messages. Message Notes can be added usingPOSTandPATCHrequests and retrieved usingGETrequests.
2016-12-12
- Added
created_atfield to/api/appointments. - Exposed primary and secondary insurance details over
api/appointments - Added
posted_dateto/api/transactions.
2016-12-21
- Added
/api/prescription_messagesendpoint. The endpoint supportsGETonly. - Added
updated_atto/api/messagesalong with aupdated_sincefilter for the same field - Added
default_pharmacyfield to/api/patientsendpoint
2017-01-17
- Added
fax_numberfield to/api/officesendpoint
2017-04-27
- Added
permissionsfield to/api/usersendpoint
2017-05-19
- Added
show_archivedfilter parameter to/api/appointmentsendpoint
2017-05-24
- Added
is_accont_suspendedfield to/api/doctorsendpoint
2017-05-25
- Added
cloned_fromfield to/api/appointmentsendpoint
2017-06-06
- Added
snomed_ct_codefield to/api/problemsendpoint - Expose
POST,PUT,PATCH, methods on/api/problems,/api/medicationsand/api/allergiesendpoints
2017-06-20
- Added
extended_updated_atfield to/api/appointmentendpoint
2017-07-02
- Added
recurring_appointmentfield andbase_recurring_appointmentfield to/api/appointmentendpoint
2017-07-21
- Added
is_walk_infield to/api/appointmentendpoint
2017-08-11
- New endpoint
/api/fee_schedulesadded
2017-08-15
- Added
nick_namefield to/api/patientsendpoint
2017-08-21
- Add
patient_flagsto/api/patientsendpoint
2017-08-21
- Added
billing_providerfield to/api/appointmentsendpoint
2017_09-18
billing_statusin/api/appointmentsendpoint now is writable.
2017-09-18
- Endpoint permission change! Read on the following endpoints,
/api/patients,/api/documents,/api/custom_demographics, now requires the same scope as write to those endpoints.
2017-09-29
- Added
doctorfield to/api/patient_payment_logendpoint
2017-10-18
- Add
/api/comm_logsendpoint
2017-10-24
- Added
sourcefield to/api/patient_payment_logendpoint - Open
/api/patient_paymentsendpoint
2017-11-04
- Added
/api/custom_insurance_plan_namesendpoint
2017-12-01
- Added
/api/inventory_categories,/api/inventory_vaccines,/api/patient_vaccine_recordsendpoints
2017-12-14
- Added
patient_statusfield to/api/patientsendpoint
2018-01-02
- Added
patient_flags_attchedto/api/patientsendpoint
2018-01-05
- Added
referring_sourcefield to/api/patientsendpoint - Added
billing_notesfield to/api/appointmentsendpoint
2018-01-09
- Added
practice_group_namefield to/api/doctorsendpoint
2018-01-11
- Added
supervising_providerfield to/api/appointmentsendpoint
2018-01-31
- Added endpoints related to Task system
2018-02-01
- Added
timezonefield to/api/doctorsendpoint
2018-02-09
- Added
show_inactivefilter to/api/patientsendpoint
2018-03-13
- Patient CCDA can be filtered with
dateanddate_rangefilter parameters
2018-03-26
- Add
sincefilter parameter to/api/clinical_note_field_values
2018-04-04
- Added
appointment,patient,posted_datefilter to/api/transactionsendpoint
2018-04-10
- Added
service_datefilter to/api/transactionsendpoint
2018-04-17
- Added
/api/line_item_transactionsendpoint
2018-04-27
- Added
/api/custom_appointment_fieldsendpoint andcustom_fieldsin/api/appointmentsendpoint
2018-04-30
- Open write access to
/api/clinical_note_field_valuesendpoint
2018-05-09
- Open CQM entries endpoints.
/api/patient_interventions,/api/patient_physical_exams,/api/patient_risk_assessments,/api/patient_communications
2018-05-23
- Open read-only
/api/lab_resultsendpoint
2018-06-05
- Added
/api/patients/:id/onpatient_accessdetail endpoint
2018-08-01
- Added
/api/staffendpoint - Added
/api/proceduresendpoint
2018-08-02
- Added
/api/implantable_devicesendpoint
2018-08-03
- Added
/api/care_plansendpoint
2018-08-03
- Added
/api/eligibilitiesendpoint
2018-09-25
Starting this day, we will be using a new version naming mechanism. Instead of calling the versions by dates, we will be using numerical versions. Please checkout our version map here for more information.
- Added lab workflow.
-
We've changed the behavior of
/api/lab_resultsendpoint a bit.- It used to require
clinicalscope, now it requireslabsscope instead. obs_codefield renamed toobservation_codeobs_descriptionfield renamed toobservation_descriptionresult_codefield renamed togroup_codetestfield deprecateddocumentfield now returns an integer ID instead of the document object.
- It used to require
-
Updated webhook verification process
2018-10-16
- Add
show_persistentfilter to/api/clinical_note_field_values
2019-01-04
- Add
/api/task_notesendpoint.
2019-07-16
- Add
allowed_valuesfield to/api/clinical_note_field_typesendpoint - Add
sincefilter to/api/line_item_transactionsendpoint
2019-07-25
- Add
archivedfield to/api/documentsendpoint - Add
profile_pictureto/api/doctorsendpoint
2019-08-09
- Add
insurance_statusfield to/api/transactionsendpoint
2019-08-28
- Add
assigned_byfield to/api/tasksendpoint - Add
status_transitionsfield to/api/appointmentsendpoint
2019-09-02
- Add
/api/billing_profilesendpoint - Add
/api/consent_formsendpoint
2019-09-17
- Add
referring_doctorfield to/api/patientsendpoint
2019-09-18
- Add
auto_accident_insuranceandworkers_comp_insuranceto/api/patientsfield
2023-05-31
When introducing the preferred_pharmacies field while retaining the default_pharmacy field, we need to ensure backward compatibility. The following behavior will be implemented:
-
Existing Default Pharmacy:
- If a patient already has a value set for the
default_pharmacyfield and the NCPDP ID of the default pharmacy exists in thepreferred_pharmacieslist, it will be automatically added to thepreferred_pharmacieslist. - If the NCPDP ID of the default pharmacy does not exist in the
preferred_pharmacieslist or is an invalid value, the default pharmacy will be set to an empty string in the patient's data. - Users will not be able to exclude the default pharmacy directly. They can remove the default pharmacy by either using the UI or removing all pharmacies from the preferred_pharmacies list.
- If a patient already has a value set for the
-
Default Pharmacy Updates:
- If the default pharmacy is updated, the new value will be automatically added to the preferred_pharmacies list if it is not already present.
- If the new default pharmacy is already present in the preferred_pharmacies list, there will be no duplication.
Note: The default_pharmacy field will be deprecated in a future version. It is recommended to use the preferred_pharmacies field to manage the patient's pharmacies. Please ensure that the NCPDP ID of the default pharmacy is valid and exists to avoid the default pharmacy being set to an empty string in the patient's data.
This backward compatibility ensures that the existing functionality of the default_pharmacy field is maintained while allowing users to manage their preferred pharmacies through the preferred_pharmacies list.
2024-03-28
Making the billing_provider and supervising_provider fields writable.