Difference between revisions of "6-0-0-4 Patch Special Instructions"

From OpenEMR Project Wiki
Line 11: Line 11:
# If you have custom patient portal templates, then you will need to re-upload these (this is documented in [[6-0-0-4_Patch_Special_Instructions#Import_existing_templates|below 'Import existing templates' instructions]]).
# If you have custom patient portal templates, then you will need to re-upload these (this is documented in [[6-0-0-4_Patch_Special_Instructions#Import_existing_templates|below 'Import existing templates' instructions]]).
<br>
<br>
See this very nice Forum post by the portal author, Jerry Padgett, for more details and instructions on the improved Patient Portal in 6.0.0 patch 4: https://community.open-emr.org/t/newly-revamped-patient-portal-v6-0-4-and-future-v6-1-0/17776
**See this very nice Forum post by the portal author, Jerry Padgett, for more details and instructions on the improved Patient Portal in 6.0.0 patch 4: https://community.open-emr.org/t/newly-revamped-patient-portal-v6-0-4-and-future-v6-1-0/17776**
<br>
<br>
<br>
<br>

Revision as of 20:10, 20 February 2022

Overview

The Patient Portal in 6.0.0 patch 4 has been significantly improved with new features:

  1. User interface improvement
  2. Patient form improvement
  3. Addition of template profiles and patient groups in order to improve delivery and organization of patient forms.


There are several new requirements in the Patient Portal with 6.0.0 patch 4:

  1. If you are using Password Reset or Patient Registration features in the patient portal, then you will need to set up Google reCAPTCHA (version 2) and then place the key and secret in the following globals respectively:
    • Administration->Globals->Portal->Google reCAPTCHA V2 site key
    • Administration->Globals->Portal->Google reCAPTCHA V2 secret key
  2. If you have custom patient portal templates, then you will need to re-upload these (this is documented in below 'Import existing templates' instructions).




Patient Portal New Features

Setting up Groups, Profiles, and Categories

This is done in Lists. the following are the list titles:

  • "Patient Groupings"
  • "Document Template Profiles"
  • "Document Template Categories"

All the lists have defaults that are general assuming user will change list titles to be more appropriate to user application of portal templates.

Import existing templates.

Once above is done you will need to import all your existing templates from the current file system at: `sites/default/documents/onsite_portal_documents/templates`. If you've templates assigned directly to patients then also upload as well. These will install to the Template Repository so you can then assign to Profiles or patient Location and/or categories.

Patient-portal-patch-1.png

The patch includes the normal default templates that shipped with previous versions of portal. They are assigned to both Repository and Default Patient Templates.

  • A quick note about Default Patient Templates. Since any template assigned here always appear in all patient portals, they will not appear in the Patient Assigned Templates view. I recommend to not use this feature(Default Patient Templates) and delete all forms, except Help, from Default Patient Templates and assign as normal templates in Profiles. Though there are many that may only need the same templates for all patients, by all means keep and add additional templates from repository. This is the reason I left this legacy feature intact.


Assign Templates.

Time to setup for template assignments. To remove item from any drag and drop dialog simply drag the item from the right panel into the left panel.

Patient Groups

Patient-portal-patch-2.jpeg
  • Drag and drop patients from left panel to appropriate group in right panel. I highly recommend using this feature because assigning templates to each patient from the location in Scope toolbar will be tedious to say the least. Plus once setup, all that is necessary to assign templates to new patients is to add patient to group on intake or registration.


Profiles

Patient-portal-patch-3.png
  • Again drag and drop the assignment. For Profile scheduling, Recurring is recommended if the template set is needed to be forms the patient needs to address more than once. If Recurring is not selected then once the patient has finished the form, it will never reappear unless sent directly.


Categories

You may assign templates to categories for further help with organizing. This is done in the Repository using the category pulldown. The effect of categories in portal is that all categories become titles in Document menu.

Patient-portal-patch-4.png
  • The red menu items means the patient has saved a document to their history and still needs to finish.


Finishing up

Once ready go to the Repository view and scroll to

Patient-portal-patch-5.png

To send or activate Profiles in portals. Note:

  • You activate Profiles that have Groups and Send profiles to Location if a profile is not assigned a Group.
  • Check the checkbox for the Profiles to activate. A button will appear anytime a change is made to a Profile checkbox .
Patient-portal-patch-6.png

Click Update and now the profiles are active in portal.

  • For profiles that haven't any Groups then the profile may be sent to one or more patients by selecting the patient(s) from the Location toolbar searchable multiselect. A Send button will appear in toolbar for sending to the Locations.
Patient-portal-patch-7.jpeg

This action has no affect on the Profiles with Groups and I probably need to hide as I do otherwise.

Patient Assigned Templates

You must select what you want to view from Location. You may select one patient, a group of patients or All Patients the click the search button. The view will show what templates are currently assigned and some status information. The only templates that may be deleted in this view are those specifically sent to the patient.

Patient-portal-patch-8.jpeg


Some other neat stuff

A couple new template directives namely

  • `{SignaturesRequired}` when added to a template with patient signature directive will force patient to sign their document before being allowed to submit document to review.
  • `{AcknowledgePdf:id or name:prompt}` for example:

Upload a pdf to repository where it will be assigned an id and template name.

Patient-portal-patch-9.png

Then create and upload a template similar to: ``` {ParseAsHTML} {SignaturesRequired} {AcknowledgePdf:80:Click to view and acknowledge} Please sign here to acknowledge you have read and understand content: {PatientSignature} ``` Resulting in a rendered portal document:

Patient-portal-patch-10.png

and

Patient-portal-patch-11.png

Of course this is example pdf and currently fillable pdf is not supported however, soon will be.