Note: throughout this article, "Client Reg" may be used as shorthand for "Client Registration"
Version Tracker
Enable Client Reg form for clinics
Review/Update Technical Documentation
Testing Information
Client Reg Form Test Set
Change Requests (CRs)
Regression Testing
Update the Test Set
Client Reg Form related EMR User Help Articles
File References
Version Tracker
Please update the table when you work on the registration form. Please follow the below instruction when you create/modify a line of the table.
- Most recent one at the top of the table
- The version number is the actual start date of the work item beginning with 'V'
- Ticket number is linked to the Jira ticket page
- Please use the same status as Jira (i.e. Analysis Active, Development Active, etc.)
- Resources are the name of the developer and the main analyst
|
Version <V.YY.MM.DD> |
Deploy Date <Analyst> |
Ticket Number <Analyst> |
Description <Analyst> |
Type <Dev> |
Name <Dev> |
Status <Dev / Analyst> |
Resource <Dev / Analyst> |
| V.26.02.09 | 3 Jun 2026 | EMR-10643 | Gender Identity box intermittently not populating | Form | Patient Registration Form (Paris)_V2 | Deployed | Edward/Leah |
| EMR-10010 | Widen Phone Fields in PIP and Phone Contact Details | ||||||
| EMR-5353 | Clear non-mandatory text fields | ||||||
| V.25.02.06 | 10 Mar 2025 | EMR-7822 | Add ISI To Profile EMR Registration Form | Form | Patient Registration Form (Paris)_V2 | Deployed | Edward/Raman |
| V.25.01.03 | 29 Jan 2025 | EMR-4234 | Make NOK and Emergency Contact information more visible in EMR | Form | Patient Registration Form (Paris)_V2 | Deployed | Gareth/Matthew |
| V.24.12.06 | 9-Dec-2024 | EMR-8199 | Client Reg: Re-add Appt Rem label behaviour | Form | Patient Registration Form (Paris)_V2 | Deployed | Edward/Leah |
| V.24.09.10 | 2-Oct-2024 | EMR-5174 | Modify Client Reg Form: Pull Primary Phone from PARIS Regardless of Phone Type PARIS |
Form | Patient Registration Form (Paris)_V2 | Deployed |
Edward/Rachelle
|
| Form | Patient Phone Numbers | ||||||
| Macro | PARISREGI_EXEC | ||||||
| Macro | G1MPS_EXEC | ||||||
| ShortCode | PARIS Contact Type | ||||||
| PAR-3642 | PARIS View | VAN_EMR_PARIS_CLIENTS_V2 | |||||
| V.24.06.14 | 3-Jul-2024 |
EMR-6375 & EMR-7231 |
Integrate Contact to Consent form & Validation for Text Consent Field |
Form | Patient Registration Form (Paris)_V2 | Deployed | Leah |
| V.23.09.21 | 28-Nov-2023 | EMR-4406 | Pronoun Integration between PARIS and Profile EMR | Form | Patient Registration Form (Paris)_V2 | Deployed | Michael/Darryl |
| Macro | PARISREGI_EXEC | ||||||
| Macro | G1MPS_EXEC | ||||||
| Form | Update Pronouns | ||||||
| Macro | PARIS_PRNL_EXEC | ||||||
| Macro | PARIS_PRNU_EXEC | ||||||
| Macro | PARISPROUN_EXEC | ||||||
| V.23.05.10 | 15-May-2023 | EMR-4484 | 8.6 Radio Button not hidden issue for client registration form | Form | Patient Registration Form (Paris)_V2 | Deployed | Edward |
| V.23.01.25 | 28-Mar-2023 | EMR-3673 | Turn on Open Photo button for all Clinics | Form | Patient Registration Form (Paris)_V2 | Deployed | Edward/Mai |
| V.22.12.16 | 13-Feb-2023 | EMR-3691 | Store MRN and MRN Type in Reg Form | Form | Patient Registration Form (Paris)_V2 | Deployed | Edward/Josie |
| V.22.10.20 | 08-Dec-2022 | EMR-3040 | Potential bug causing records to share the same PID | Form | Patient Registration Form (Paris)_V2 | Deployed | Edward/MariLen |
| V.22.10.18 | 08-Nov-2022 | EMR-2000 | Client Search Form (Search by Phone) | Form | Client Search Form | Deployed |
Edward/Teresa
|
| Form | Patient Registration Form (Paris)_V2 | ||||||
| Macro | PARISMA_V2_EXEC | ||||||
| V.22.09.02 | 04-Oct-222 | EMR-3028 | Update Label "External Family Physician/NP" | Form | Patient Registration Form (PARIS)_V2 | Deployed | Josie/Michael |
| V.22.05.18 | 18-Aug-22 | EMR-2957 | Prevent Users from Creating Test Clients in Reg Form | Form | Patient Registration Form (Paris)_V2 | Deployed | Edward/David |
| Client Search Form | |||||||
| V.22.05.13 | 18-May-22 | EMR-2226 | Fixes Photo Tool Button | Form | Patient Registration Form (Paris)_V2 | Deployed | Edward/Edwin |
| V.22.05.09 | 02-Jun-22 | EMR-2186 | Client Reg Form (First Save Bug) | Form | Patient Registration Form (Paris)_V2 | Deployed | Edward/Teresa |
| V.22.04.06 | 31-May-22 | Update Alerts on Yellow Bar | Form | Patient Registration Form (Paris)_V2 | Deployed | Edward/Josie | |
| Form | Patient Alerts Form | ||||||
| Macro | PARIS_ALTE_EXEC | ||||||
| Macro | PROB_POSTPROC | ||||||
| V.22.03.31 | 04-May-22 | EMR-2335 | Client Reg Form NOK updated to populate Clinical Summary > Family History | Form | Patient Registration Form (Paris)_V2 | Deployed | Henry/Edwin |
| EMR-2355 | Client Reg Form GCO Clients and Alias | Edward/Teresa | |||||
| V.22.03.09 | 16-Mar-22 | EMR-1876 | Update List of Alerts pulled from PARIS | Form | Patient Registration Form (Paris)_V2 | Deployed | Michael/Teresa |
| Form | Patient Alerts Form | ||||||
| Macro | PARIS_ALTE_EXEC | ||||||
| Macro | G1MPS_EXEC | ||||||
| V.22.01.18 | 18-Jan-22 | EMR-572 | Next of Kin stored in EMR (210634) (PC3560) | Form | Patient Registration Form (Paris)_V2 | Deployed | Michael/Edwin |
| Form | Update NOK | ||||||
| Macro | G1MPS_EXEC | ||||||
| V.21.10.28 | 28-Oct-21 | EMR-721 | Gender Inclusion - Reg Form and Yellow Bar Updates | Form | EMR Patient List (Paris)_V2 | Deployed | Edward/Josie |
| Form | Patient Registration Form (Paris)_V2 | ||||||
| Form | Client Search Form | ||||||
| Form | Update Gender Identity | ||||||
| Form | Update Pronouns | ||||||
| Form | Gender Identity Panel | ||||||
| Macro | CLIENTREG_PARIS | ||||||
| Macro | G1MPS_EXEC | ||||||
| Macro | PARISMA_V2_EXEC | ||||||
| Macro | PARISREGI_EXEC | ||||||
| Macro | PROB_POSTPROC | ||||||
| Print Variable | CLIENTGENIDNTY | ||||||
| Print Variable | CLIENTPRONOUNS | ||||||
| Short Code | Client Gender Identity | ||||||
| Short Code | Client Pronouns | ||||||
| V.21.10.28 | 28-Oct-21 | EMR-1654 | BCCDC - Suppress Alt POS on Registration | Form | Patient Registration Form (Paris)_V2 | Deployed | Edward |
| V.21.09.09 | 9-Sep-21 | EMR-724 | Saving Alerts created in the Client Registration Form | Form | Patient Registration Form (Paris)_V2 | Deployed | Edward/Josie |
| Form | Patient Alerts Form | ||||||
| V.21.08.23 | 23-Aug-21 | EMR-1473 | Client Registration Form - GCO Client Bug | Form | Patient Registration Form (Paris)_V2 | Deployed | Edward/Teresa |
| Form | Client Search Form | ||||||
| V.21.07.07 | 7-Jul-21 | EMR-1669 | Allow Apostrophes in Client Names (Client Registration Form) | Form | Patient Registration Form (Paris)_V2 | Deployed | Edward/Teresa |
| Form | Client Search Form | ||||||
| V.21.06.24 | 24-Jun-21 | EMR-1650 | Client Registration Form & PARIS Update Macro | Form | Patient Registration Form (Paris)_V2 | Deployed | Edward |
| (Adding gender X) | Form | Client Search Form | |||||
| V.21.04.09 | 9-Apr-21 | EMR-1471 | Client Registration form database mapping issue (EMR Support) | Form | Patient Registration Form (Paris)_V2 | Deployed | Edward |
| Form | Client Search Form | ||||||
| Short Code | Database Map | ||||||
| V.21.02.04 | 4-Feb-21 | EMR-886 | Client Registration Form Changes for GCO Post-Process Macro | Form | Patient Registration Form (Paris)_V2 | Deployed | Henry/Teresa |
| Form | Client Search Form | ||||||
| V.21.01.25 | 25-Jan-21 | EMR-1177 | HiM POS - addition of indeterminate and pseudonym to the client record type in the Registration form | Form | Patient Registration Form (Paris)_V2 | Deployed | Edward/Jaclyn |
| Short Code | Client Reg Form Record Type | ||||||
| V.20.11.02 | 2-Nov-20 | EMR-826 | PARIS Alerts not showing in the Client Registration Form | Form | Patient Registration Form (Paris)_V2 | Deployed | Edward/Josie |
| V.20.10.29 | 29-Oct-20 | EMR-1008 | Registration form alerts creation bug fix | Form | Patient Registration Form (Paris)_V2 | Deployed | Edward/Teresa |
| V.20.02.06 | 6-Feb-20 | PC2424 | Remove Association between EMR and Paris | Deployed | |||
| - Setup generic referral in Paris | |||||||
| - Batch create Generic Referral | |||||||
| - Batch discharge EMR Generic Referrals in Paris | |||||||
| - Created Client Search form | |||||||
| - Patient registration form and client list form are modified to Version2 | |||||||
| V.19.12.12 | 12-Dec-19 | PC3453 | Update Gender Identity Code | Form | Patient Registration Form (Paris) | Deployed | |
| DMT203873 | |||||||
| V.19.12.02 | 2-Dec-19 | PC3412 | Increasing photo resolution | Form | Patient Registration Form (Paris) | Deployed | |
| V.19.11.14 | 14-Nov-19 | PC3394 | No match found bug fix | Form | Patient Registration Form (Paris) | Deployed | |
| V.19.07.16 | 16-Jul-19 | PC3211 | Bug, null Paris referral reason | Form | Patient Registration Form (Paris) | Deployed | |
| DMT190492 | |||||||
| V.19.06.18 | 18-Jun-19 | PC3152 | Adding Photo function for PEN | Form | Patient Registration Form (Paris) | Deployed | |
| DMT184462 | |||||||
| V.19.03.13 | 14-Mar-19 | PC4090 | Phase 2 update | Form | Patient Registration Form (Paris) | Deployed | |
| DMT171508 | - Register client from EMR | Form | Patient Alerts Form | ||||
| - Alerts added | Macro | CLIENTREG_PARIS | |||||
| - MPR, POS updatable | Macro | G1MPS_EXEC | |||||
| - Discharge Paris referral | Macro | PARIS_ALTE_EXEC | |||||
| - Send EMR user info to Paris | Macro | PARISREGI_EXEC | |||||
| V.18.12.17 | 17-Dec-18 | PC2693-68 | Record type incident | Form | Patient Registration Form (Paris) | Deployed | |
| DMT170539 | |||||||
| V.18.12.13 | 13-Dec-18 | PC2693-64 | HIM Request Changes | Form | Patient Registration Form (Paris) | Deployed | |
| DMT169282 | |||||||
| V.18.10.30 | 30-Oct-18 | PC2693-63 | Incident, removing PHN issue | Form | Patient Registration Form (Paris) | Deployed | |
| DMT165515 | |||||||
| V.18.20.25 | 25-Oct-18 | PC2693-60 | Incident, PHN issue | Form | Patient Registration Form (Paris) | Deployed | |
| DMT164996 | Macro | PARISMATCH_EXEC | |||||
| V.21.04.10 | 10/4/2021 (?) | PC2693-57 | Allowing Numeric for names | Config | Sys-config | Deployed | |
| V.18.10.18 | 18-Oct-18 | PC2693-55 | Revision Address Fix | Macro | G1MPS_EXEC | Deployed | |
| DMT162824 | Macro | CLIENTREG_PARIS | |||||
| Macro | PARISREGI_EXEC | ||||||
| Form | Patient_List(PARIS) | ||||||
| Form | Patient Registration Form (Paris) | ||||||
| V.18.08.20 | 20-Aug-18 | PC2693-50 | Revision PHN removing | Macro | PARISREGI_EXEC | Deployed | |
| Form | Patient List Form | ||||||
| Form | Patient Registration Form | ||||||
| V.18.08.15 | 15-Aug-18 | PC2693-47 | Bug Fix | Form | Patient Registration Form | Deployed | |
| DMT147823 | Modified function | Termset | VCH_PCCEMR | ||||
| Macro | G1MPS_EXEC | ||||||
| Macro | PARISREGI_EXEC | ||||||
| ? | PC2693-39 | Paris change for client search | Deployed | ||||
| ? | PC2693-25 | NOK Address Postal Code | Form | Patient Registration Form | Deployed | ||
| ? | PC2693-25 | Bug Fix | Form | Patient Registration Form | Deployed | ||
| Macro | PARISMATCH_EXEC | ||||||
| Macro | PARISREGI_EXEC | ||||||
| V.18.03.09 | ? | PC2693-24 | Bug Fix | Form | Patient Registration Form | Deployed | |
| Form | Patient List Form | ||||||
| Macro | PARISMATCH_EXEC | ||||||
| V.18.03.08 | 8-Mar-18 | PC2693-13 | Initial Version_fixed | Form | Patient List Form | Deployed | |
| DMT136127 | Form | Patient Registration Form | |||||
| SC | Ethnicity | ||||||
| SC | Forms | ||||||
| SC | Registry Key | ||||||
| Termset | VCH_PCCEMR | ||||||
| Macro | CLIENTREG_PARIS | ||||||
| Macro | PARIS_ID_EXEC | ||||||
| Macro | PARIS_MIG_EXEC | ||||||
| Macro | PARISMATCH_EXEC | ||||||
| Macro | PARISREGI_EXEC | ||||||
| V.17.12.04 | 4-Dec-17 | PC2830 | Initial Version | Form | Patient Registration Form (Paris) | Deployed | |
| Macro | PARIS_MIG_EXEC | ||||||
| Macro | PARISREGI_EXEC |
Enable Client Reg form for clinics
To enable the Client Reg form, all that is required is to insert this short code item:
- Short Code Type = PARIS Referral Reason
- Code = <POS code>
- Description = <leave blank>
Review/Update Technical Documentation
If a work item impacts/changes the Client Registration form or any supporting forms like Client Search, the technical documentation should be reviewed. It can be used by the developer to understand the components where the work impacts.
It is the responsibility of the developer to update the documentation to ensure accuracy. On top of creating the dev subtask, the lead analyst should also create a separate subtask for this work.
-
Lead Analyst to create subtask for the related JIRA:
- Subtask name: Review/Update Client Reg Tech Document
- Assignee: developer
-
Developer steps:
- Download the technical document at the bottom of this article under File References
- Review the areas of impact from the work item. If the area requires an update after development:
- Make appropriate changes
- In editor mode, replace document in this article (if need assistance, ask Leah)
- Update the "Last Updated Date" at the bottom of the article
- Publish article
Testing Information
Client Reg Form Test Set
The test set is saved under the Functional Test Cases folder:
Change Requests (CRs)
For all CRs impacting the Client Reg form, follow these guidelines in preparing the CR's Test Run:
- In TestRail, copy the 1. Client Reg - Core Testing Set folder and all its contents into the CR's test folder. These cases must be included in all CR test runs.
- Reminder to update the version ID in the preconditions of the copied POS Access Rights to Correct Client Reg Form
- Reminder to update the version ID in the preconditions of the copied POS Access Rights to Correct Client Reg Form
- Copy the folder section(s) that are impacted by the change(s) of the CR into the CR's test folder. E.g., if the Consent to Contact Phone Number logic was updated, copy over the 4. Client Reg - Section: Contact folder and all its cases
- Consult with the developer if the code change impacts more than the obvious section of the Client Reg form. All sections specified by the developer should be copied.
- This is to ensure no side effects were created by the CR.
- Create test cases targeted specifically for the CR in the CR's test folder. Ensure that these capture scenarios with the most realistic workflow followed by users. E.g., logged in as a CSC/CA, using appropriate test data values, etc.
Regression Testing
During regression testing for build upgrades, use the entire test set.
Update the Test Set
After the testing phase is completed or the CR is deployed, the lead analyst should review the targeted cases for integration into the Client Reg form test set. Consider the following:
- Are any components of the targeted test cases helpful in future CR and/or regression testing?
- Are all test cases/scenarios needed to be part of the Test Set? Often times, the targeted test cases are much more granular than required for regressing testing or CR impact testing.
- Can an existing test case be leveraged (i.e. similar case but only need to add/adjust a few steps)? If yes, update the existing test case(s).
- If a case should be added, ensure it is filed under the appropriate section folder and inserted into a logical place on the list (ideally the future tester would run the cases sequentially).
Client Reg Form related EMR User Help Articles
- Client Registration Form – Profile EMR User Help (zendesk.com)
- Streamlined Client Registration – Profile EMR User Help (zendesk.com)
- EMR Registration Form – BCCDC CPS – Profile EMR User Help (zendesk.com)
File References
- Client Registration Form Technical Specifications (Last Updated 2026-06-11)
Reminder to devs to review this document for every Client Reg related work. Update if needed.