Upon sign-up and registration, we need to be able to store the Patient resource in an intermediate location.
1. User submits signup, which we will need to respond with appropriate Auth data, and store extra data in intermediate location on the Auth Server's DB:
Description:
Sign-Up Screen will allow a user to sign up and set a password for using as login credentials together with a username
Acceptance Criteria:
{color:#205081}1) Content{color}
a) First Name - type: input text field (First Name placeholder or equivalent i.e field description); Validation - only letters and special characters allowed, length limited as per OpenEMR limitations
b) Surname - type: input text field (Last Name placeholder or equivalent i.e field description); Validation - only letters and special characters allowed, length as per OpenEMR limitations
c) Gender - type: dropdown field or equivalent allowing to select either "male" or "female"
e) Mobile Number - type: input number field, Validation - only number allowed (numeric keyboard opens) with length of 10 characters starting with "0"
f) Email address - type: input text field, validation - only allow for email format i.e x@x.x, length as per openEMR limitations
g) Password - type: text/number - the password needs to be strong as per file attached (Tony has provided)
h) Confirm Password
g) Button labeled "Submit" or equivalent ^1^ - type: button
h) "a button for exiting the screen" if required by the user, it may be implemented differently for iOS and Android phones due to different design guidance
^1^ - Submit button will only appear once all required information are entered
{color:#205081}2) Navigation{color}
Submit - once tapped on and all data validation passed a pop-up message will appear stating "You have been successfully signed up and can now login to the application";
"a button for exiting the screen" - once tapped on a warning message will appear "Are you sure you want to cancel the sign up process?". The warning pop-up message will have Yes/No options. If selecting Yes, the user will be returned to MSGPOL-5 Log in Screen, selecting "No" will close the pop-up message
{color:#205081}3) Other {color}
a) validation will be performed on element blur
b) T&C will be static and hardcoded for this phase of this project
2. After sign-up, the User will "Register" their profile. Grouped by the General Practitioner (Provider) we need to store that user's Patient resource in the appropriate EHR database
Here we will figure out the Patient's Provider by parsing the FHIR request. We will have to map the Patient to an EHR database using a mapping table that maps Providers to Databases. Once we figure out the database to connect to, then we will store that database link in the user's credentials, along with a newly created patient ID in that database, and then store the "registration" data inside the EHR database that we have mapped the patient to (based on their provider.)
Upon sign-up and registration, we need to be able to store the Patient resource in an intermediate location.
1. User submits signup, which we will need to respond with appropriate Auth data, and store extra data in intermediate location on the Auth Server's DB:
Description:
Sign-Up Screen will allow a user to sign up and set a password for using as login credentials together with a username
Acceptance Criteria:
{color:#205081}1) Content{color}
a) First Name - type: input text field (First Name placeholder or equivalent i.e field description); Validation - only letters and special characters allowed, length limited as per OpenEMR limitations b) Surname - type: input text field (Last Name placeholder or equivalent i.e field description); Validation - only letters and special characters allowed, length as per OpenEMR limitations c) Gender - type: dropdown field or equivalent allowing to select either "male" or "female" e) Mobile Number - type: input number field, Validation - only number allowed (numeric keyboard opens) with length of 10 characters starting with "0" f) Email address - type: input text field, validation - only allow for email format i.e x@x.x, length as per openEMR limitations g) Password - type: text/number - the password needs to be strong as per file attached (Tony has provided) h) Confirm Password g) Button labeled "Submit" or equivalent ^1^ - type: button h) "a button for exiting the screen" if required by the user, it may be implemented differently for iOS and Android phones due to different design guidance
^1^ - Submit button will only appear once all required information are entered
{color:#205081}2) Navigation{color}
Submit - once tapped on and all data validation passed a pop-up message will appear stating "You have been successfully signed up and can now login to the application";
"a button for exiting the screen" - once tapped on a warning message will appear "Are you sure you want to cancel the sign up process?". The warning pop-up message will have Yes/No options. If selecting Yes, the user will be returned to MSGPOL-5 Log in Screen, selecting "No" will close the pop-up message
{color:#205081}3) Other {color}
a) validation will be performed on element blur b) T&C will be static and hardcoded for this phase of this project
2. After sign-up, the User will "Register" their profile. Grouped by the General Practitioner (Provider) we need to store that user's Patient resource in the appropriate EHR database
Here we will figure out the Patient's Provider by parsing the FHIR request. We will have to map the Patient to an EHR database using a mapping table that maps Providers to Databases. Once we figure out the database to connect to, then we will store that database link in the user's credentials, along with a newly created patient ID in that database, and then store the "registration" data inside the EHR database that we have mapped the patient to (based on their provider.)