Alter system generation of CORI process
Document Status | COMPLETED |
---|---|
Document Owner | @Robert Adach |
Business POC |
|
Related Document Links |
|
Azure Dev Ops Work Item # |
Description
With the changes to the Massachusetts board as mentioned in MA License file automation process , a new process has been requested and discussed with ASWB regarding the processing of CORI reports. Currently, requests for CORI review by DPH occurs when the CORI report is scanned and the “Export CORI” report is run. Today an application can be included on this file regardless of the status the application is in.
The board and MERS team has agreed that an application must appear only after the applicant has been billed for their license (application resides in Billed status)
Assumptions
This change applies to the CORI reports for both LAPMgr systems
The columns/data in files produced for transmission to DPH will not be changed.
The processing of the responses from the DPH does not change
Requirements
CORE
Ensure that applications are included on the CORI report only when the application is in billed status.
Ensure that applications can be moved to Billed status without a Pass or fail response
Ensure that content on Legacy LAPMgr application has been updated.
Ensure that ASWB staff has access to the new site used for communicating results.
Update all necessary email templates used if needed to reflect the change in process.
Design Considerations
There are to be no visual changes to the LAPMgr or PreApp program
Questions/Tasks
Question | Respondent | Answer | |
---|---|---|---|
1 | Is the generation of a SORBS report affected by this change? | Dave | Per email from Dave and the DPH team, there are no changes to the format of either reports other than the filtering of applications in Billed status.
|
2 | Do we need PreApp changes | Dave//Keeley | No |
3 | Review all email templates to determine any content changes advising applicant of changes to process | MERS |
|
4 | IT will to team with the current CORI and new filtered CORI | IT | Attached as US2188 - CORIReport.xlsx |
5 | How will system handle situations where the CORI fails and application needs to be sent to the board |
| We have two options
|
Timeline
Action | Date |
| |
---|---|---|---|
1 | Activate new query in production | 1/31/2023 | Testing of change through LAPTest connection was skipped per business |
2 | Provide updated content for templates to IT | 1/30/2023 |
|
3 | Provide updated contact for website to IT | 1/30/2023 | Not in original scope |
4 | Update email templates | 2/9/2023 | Done |
5 | Update website content | TBD | Done |
Test Cases
Link to test case documentation | Result | |
---|---|---|
1 |
| NOT TESTED | FAILED | PASSED |
2 |
|
|
Supporting Documentation
Related Items