Potential Patient Safety
Blueprints Overwrite Chief Complaint Custom Form Data from Patient Portal Custom Check-in
Release Date
May 3, 2021
Known Issue #
KI199362
Issue
In NextGen® Office EHR, when a blueprint contained a Chief Complaint custom form that was also used in the NextGen Office Patient Portal custom check-in process, the blueprint data overwrote the data that was entered by the patient during the Patient Portal custom check-in process.
Steps to Reproduce
- Set up a Patient Portal custom check-in process that includes a Chief Complaint custom form.
- Make an appointment for a patient with a Patient Portal account using the appointment type tied to the Patient Portal custom check-in process created in step 1.
- Create a blueprint using the Chief Complaint custom form.
- The patient checks in for the appointment from their portal account, making sure to complete the Chief Complaint custom form with different data than was saved in the blueprint (step 3).
- In the patient's encounter, confirm that the data submitted during Patient Portal check-in has been populated.
- Click Grand Central and select the blueprint created in step 3.
Patient Portal data does not show on the pre-import screen.
- Click Import.
- Click Preview Encounter.
The data from the Patient Portal custom check-in has been changed to the data saved in the blueprint.
Action Required
Do not save the Chief Complaint custom form in the blueprint if that Chief Complaint custom form is also used in the Patient Portal custom check-in process.
Status
This issue was fixed on November 17, 2022.
Clients who are experiencing this issue can link their practice to this issue via the NextGen Healthcare Success Community homepage. Navigate to the Known Issues tab, select the known issue that is affecting your practice, and select the This Known Issue Affects me check box. A case will be created on your behalf and you will be kept updated on the status of this issue.
