Magic Edit is designed to make your documentation process faster and more intuitive. By following the steps outlined below, you can prompt Magic Edit with your own instructions to make your note-editing process more efficient and tailored to your specific requirements.
Step 1) Access Magic Edit
Locate the 'Magic Edit' button within your document interface. This button is visible when viewing any processed note.
Step 2) Activate Magic Edit
Click on the 'Magic Edit' button. A popup box will appear, allowing you to enter your instructions via text ( 1 ) or voice by clicking on the mic icon ( 2 ).
Step 3) Enter Instructions to Edit Your note
You can speak or type your instructions into the Magic Edit popup box. Once you've entered your instructions, click 'Update Note' (if using text prompt) or 'End Instructions' (if using voice prompt).
Tips for Using Magic Edit
Be Clear and Specific: Clearly request the changes you need and for which note section (Subjective, Objective, Assessment and Plan, or Patient Instructions). The more specific your instructions, the more accurately Magic Edit will perform.
One Instruction at a Time: Giving one instruction at a time may provide better results and make for faster processing time.
Review Changes: After using Magic Edit, quickly review the updated note to ensure all changes have been correctly applied. You can click 'Undo' to revert back to the previous version.
Examples of Magic Edit prompts
Add information to a note section
Add a normal ROS template to the Subjective section and include all 14 systems
Add the following labs and physical exam findings to the Objective section...
Update the Assessment and Plan section to include...
Change the patient pronouns
Change pronouns from "they/them" to "she/her" throughout the entire note
Edit the patient name
Change the patient's name from "John" to "Jon" throughout the entire note
Change "the patient" to "John" throughout the entire note
Remove information from a note section
Update the Assessment and Plan section by removing [issue #1] and [issue #2] from the problem list