12.1 Bi-weekly Release: Updated Endpoints: Backend Updates to PRAPARE Screener


Backend updates to PRAPARE screener


athenaClinicals, athenaCommunicator, athenaClinicals for Hospitals & Health Systems




December 1, 2022


We are making updates to an answer-level code mapping in the PRAPARE screener. There will be no noticeable change for clients, but version numbers will change. Similar to our Social History note a few months ago, clients should not be impacted if coding based on keys versus version numbers. 


  • N/A

Is this a breaking change

No, this is not a breaking change

Endpoints affected

  • GET/ Get list of past screening questionnaires for a patient

New Endpoints

  • N/A


Refer to the following resources for more information:

What is changing

We are making changes to the following PRAPARE questions:

  • Has lack of transportation kept you from medical appointments, meetings, work, or from getting things needed for daily living?
    • Answer: Yes it has kept me from medical and non-medical appointments.

These changes will not impact question keys. .

Why we’re making the change

We’re making this change to PRAPARE as part of a quality measure. 

What will current users of the endpoint need to update in their code

If you are using question keys as a means of passing information via an API, there will be no impact or action needed as all keys and languages will be the same. However, if you are using Question IDs, Form IDs, or Version Numbers, these codes should be updated to match the new Version Numbers. 

What will happen if users of the endpoint do not update their code

This is not a breaking change for users using keys, so nothing will happen if changes are not made. If users are using Question IDs, Form IDs, or Version Numbers and do not update their code, data retrieval and delivery to these endpoints may be disrupted.

Was this information helpful? Yes | No Thank you for your feedback! What went wrong? Incomplete or incorrect information | Irrelevant Content | Others

On this Page