Patient Intake and Check-in

Patient Portal now provides additional patient intake and check-in support.

• Patient Portal users can register before their appointment.
• New Patient Portal users are invited to create an account.
• Users can switch language or read the Terms of Use and privacy policies documents from the log-in page or while completing the registration process.
• Patient Portal users can check in to an appointment 30 minutes before the appointment starts until 15 minutes after the appointment starts (by default).
• Patient Portal users can sign consent forms after completing the patient intake process.

Solution Change	Description and UI Impact	Reference Materials	Validation Guidelines	Implementation and Maintenance Impact
Integration with Patient Portal (HLG2-1162)	Patient Portal users can register before their appointment. By default, the registration period starts 3 days before the scheduled appointment and ends 15 minutes after the check-in period begins. UI Impact (Workflow - Automatic): Users can select Register on applicable appointment cards on the Home or Appointments dashboard to start the registration process. See the Reference Materials for more information.	See the Registering and Checking in for an Appointment topic in the Oracle Health Patient Portal Cloud Service User Guide for Patients for Patients for more information.	Verify that if a patient has an upcoming appointment (within 3 days) and is signed into the portal, The user sees the upcoming appointment in the Next Appointments section of the Appointments dashboard with the ability to register for the appointment.	No implementation or maintenance impact.
Pages are Contextualized for Authorized Representatives (HLG2-1163)	The Patient Portal registration process recognizes when someone is completing the workflow as an authorized representative. UI Impact (Workflow - Automatic): Patient Portal users can switch accounts from the Profile (Switch User) page. After switching accounts, the registration process displays information for only the selected patient account. See the Reference Materials for more information.	See the Registering and Checking in for an Appointment topic in the Oracle Health Patient Portal Cloud Service User Guide for Patients for more information.	For authorized representatives, verify that the registration process is specific to the user, as well as the patient.	No implementation or maintenance impact.
Invitation to Create Patient Portal Account (HLG2-1506)	Patient Portal users who do not have a portal account established can be invited to create a portal account and sign in to Patient Portal. This process can be performed only on established patients that have been seen in office (patients who have met the threshold of identity proofing). UI Impact (Workflow - Automatic): After the registration process is complete, Patient Portal users who do not have a portal account established are given an option to create a Patient Portal account. If the user decides to create a portal account: The user is redirected to complete the enrollment and Invitation workflow. The system passes to enrollment the demographic information such as first name, last name, date of birth, contact information, and medical record number (MRN). See the Reference Materials for more information.	See the following reference materials for more information: Accepting Invitations and Enrolling topic in the Oracle Health Patient Portal Cloud Service User Guide for Patients Registering and Checking in for an Appointment topic in the Oracle Health Patient Portal Cloud Service User Guide for Patients	Verify that if a patient does not yet have an established Patient Portal account, the user will be invited to enroll at the end of the patient Intake workflow.	No implementation or maintenance impact.
Terms of Use and Privacy Policy (HLG2-1507)	Patient Portal users can view their organization's Terms of Use and privacy policy while completing the registration process. UI Impact (Workflow - Automatic): Patient Portal users can access the Terms of Use and privacy policy from links on the identity verification page during the registration and check-in workflows. See the Reference Materials for more information.	See the Registering and Checking in for an Appointment topic in the Oracle Health Patient Portal Cloud Service User Guide for Patients for more information.	Verify that Patient Portal users can view their organization's Terms of Use and privacy policy while completing the registration process.	No implementation or maintenance impact.
Language Switcher (HLG2-1514)	Patient Portal users can switch the language to another supported language while completing the registration process. UI Impact (Workflow - Automatic): Languages are switched from the Sign-In page and on the identity verification page of the patient Intake and Consumer Check-In workflows. After switching language, the registration process displays all information in that language. See the Reference Materials for more information.	See the following reference materials for more information: Managing Accounts and Profiles in Your Patient Portal topic in the Oracle Health Patient Portal Cloud Service User Guide for Patients Registering and Checking in for an Appointment topic in the Oracle Health Patient Portal Cloud Service User Guide for Patients	Verify that Patient Portal users can switch the language while completing the registration process.	No implementation or maintenance impact.
Check-in From Next Appointments (HLG2-2053)	Patient Portal users can check in for an appointment. The check-in period begins 30 minutes before the appointment begins and ends 15 minutes after the appointment starts by default. UI Impact (Workflow - Automatic): Patient Portal users can check in for an appointment by selecting Check In on an appointment card. See the Reference Materials for more information.	See the Registering and Checking in for an Appointment topic in the Oracle Health Patient Portal Cloud Service User Guide for Patients for more information.	Verify that a check-in action is displayed on the Upcoming Appointments section of the Appointments dashboard 30 minutes before the appointment start time, and is no longer displayed after 15 minutes pat the appointment start time.	No implementation or maintenance impact.
eSignature Capabilities in the Limited Authentication Patient Intake Workflow (HLG2-3676)	eSignature capabilities are available in the patient intake workflow for limited-authentication portal users. UI Impact (Workflow - Automatic): Consent forms occur during the preregistration workflow after the Responsible Party guided process step and can be optionally skipped by users.	See the following resources for more information: Registering and Checking in for an Appointment topic in the Oracle Health Patient Portal Cloud Service User Guide for Patients for more information. Oracle Health Patient Administration Configuration User Guide	Verify that during patient intake, fully authenticated users see consent forms displayed after Health History and can optionally skip these forms.	Implementation Impact: Low Forms can be configured in Oracle Health Patient Administration Configuration. Maintenance Impact: Low Forms can be maintained and edited using Oracle Health Patient Administration Configuration. See the Reference Materials for more information.
eSignature Capabilities in the Full Authentication Patient Intake Workflow (HLG2-3677)	eSignature capabilities are available in the patient intake workflow for fully authenticated portal users. UI Impact (Workflow - Automatic): Consent forms occur during the preregistration workflow after the Responsible Party guided process step and can be optionally skipped by users.	See the following resources for more information: Registering and Checking in for an Appointment topic in the Oracle Health Patient Portal Cloud Service User Guide for Patients for more information. Oracle Health Patient Administration Configuration User Guide	Verify that during patient intake, fully authenticated users see consent forms displayed after Health History and can optionally skip these forms.	Implementation Impact: Low Forms can be configured in Oracle Health Patient Administration Configuration. Maintenance Impact: Low Forms can be maintained and edited using Oracle Health Patient Administration Configuration. See the Reference Materials for more information.
eSignature Capabilities in the Limited Authentication Check-in Workflow (HLG2-3678)	eSignature capabilities are available in the check-in workflow for limited-authentication portal users. UI Impact (Workflow - Automatic): Consent forms occur during the preregistration workflow after the patient intake's Responsible Party guided process step and can be optionally skipped by users.	See the Registering and Checking in for an Appointment topic in the Oracle Health Patient Portal Cloud Service User Guide for Patients for more information.	Verify that during check-in, fully authenticated users see consent forms displayed after Health History and can optionally skip these forms.	Implementation Impact: Low Forms can be configured in Oracle Health Patient Administration Configuration. Maintenance Impact: Low Forms can be maintained and edited using Oracle Health Patient Administration Configuration. See the Reference Materials for more information.
eSignature Capabilities in the Full Authentication Workflow (HLG2-3679)	eSignature capabilities are available in the check-in workflow for fully authenticated portal users. UI Impact (Workflow - Automatic): Consent forms occur during the preregistration workflow after the patient intake's Responsible Party guided process step and can be optionally skipped by users.	See the Registering and Checking in for an Appointment topic in the Oracle Health Patient Portal Cloud Service User Guide for Patients for more information.	Verify that during check-in, fully authenticated users see consent forms displayed after Health History and can optionally skip these forms.	Implementation Impact: Low Forms can be configured in Oracle Health Patient Administration Configuration. Maintenance Impact: Low Forms can be maintained and edited using Oracle Health Patient Administration Configuration. See the Reference Materials for more information.