Incident-To Practitioner Enhancement - MedNote

This article describes a 2024 planned feature delivered through the myAvatar Product Roadmap. This information is subject to change.

What are we doing?

When a resident sends a medical note to the supervising provider and the supervising provider signs the note, a service will still be generated in the billing_tx_history table. This service will record the provider entered in the staff member search as the incident_to_pract_ID and incident_to_pract_name fields, and the resident will be recorded as the provider_ID and provider_name fields in the billing_tx_history table. 

Additionally, when a note is finalized by the supervising provider, the author of the note will display as the resident rather than the supervising provider. 

Why are we doing it?

Today, when a resident routes a medical note to the supervising provider and the supervising provider signs the note, a service is created in the billing_tx_history table. The service is incorrectly writing the supervising provider as the provider_ID and provider_name fields in the billing_tx_history table and does not list the resident at all. 

Additionally, when a resident writes a note and sends it to their supervisor to add an attestation and finalize, the author of the note will display as the supervisor and not as the resident.  

How are we doing it?
When the Enable Incident-To Practitioner registry setting is set to Yes, Medical Note will write the resident user to the Provider_ID and Provider_Name column in the billing_tx_history table instead of the supervising provider name and ID.

When the Enable Incident-To Practitioner registry setting is set to Yes, Medical Note will not write the supervising provider to the provider_ID and provider_name column in the billing_tx_history table. The supervising provider will only be used for routing the note for finalization.  

When the staff member is filled in using the Site-Specific Section Modeling in Medical Note, save the user to the incident-to practitioner columns in the billing_tx_history table.