Build Process

A standardized process outlines steps that should be followed to bring an idea into production. The recommended process emphasizes transparency and expert review, allowing issues to be identified and addressed early on. By following a standardized process, Builders can consistently deliver high-quality work.

Build Process for Operational Content

A AHS Clinical Content Builder Program Workflow Map highlights responsibilities and roles for Clinical Builders. Of course, there may be project-specific nuances that stray from the map. When significant, those should be reviewed with partner analysts or at Builder support scrums or office hours. 

Links to additional information

1. Projects can come in through a variety of means, however all requests should be tied back to a ServiceNow Ticket. Continuous Improvement projects use the JIRA ticketing system.

2. Tickets can be brought by Builders to the SCRUM Meetings or emailed to the program for review

3. Information on JIRA Continuous Improvement Tickets,  Builder Scope, using JIRA as a Builder, JIRA Ticket page

4. By Builder or via SCRUM. Specific Builder is assigned on the IT App Support tab in JIRA.

5. Can be facilitated by leads, the Builder or others.

6. Build environments and purpose

Content Management SharePoint , CM as a Builder, AHS Change Management presentation

7. Done with guidance from application leads

8. Discussed in step 5

9. Discussed ownership in step 5. Integrated Application Testing 

10. Discussed in step 5, Epic Testing Strategy Handbook

11. JIRA Ticket page

12. Discussed in step 5

13. Training tab in JIRA, 

14. Can be facilitated by Builder, Clinical Informatics Lead, or other Links to Data Courier, Change Process Email, Content Management SharePoint, Epic Data Migration Handbook

15. Similar to step 15

16. JIRA Ticket page

Build Process for Inquiry Content

Clinical Builders may be involved in or otherwise engaged to contribute to Connect Care clinical content build that will serve the purposes of a formal inquiry (research) initiative. In such cases, other processes and accountabilities may pertain.

The ASH Health System Access (HSA) team plays a pivotal role in facilitating research access to the Connect Care instance of Epic Systems, as well as other enterprise information systems. HSA assists with data extract requests and In-System reporting. 

Builders may be approached by investigators or clinicians seeking custom build for inquiry purposes. They should communicate early with HSA to determine the type of inquiry and whether the requester should be directed to HSA or other support groups. Stakeholders can expect a prompt response from a member of the HSA team who will guide them through appropriate steps to an effective process. AHS Clinician Builders may be approached by HSA to continue involvement, but with an explicit process and resource accountability guided by HSA.

HSA support extends beyond builds into data access and analysis. For a more comprehensive understanding of the services offered by HSA, interested parties are encouraged to visit the Provincial Health System Access website (Intranet) or explore AHS IT Access for Research resources, including an intake form for new support requests.

• Contact: research.administration@ahs.ca

Build Process for Documentation of New Reporting Content

To document new reporting content, the Builder must complete a report overview form, which is then the source of truth and added as a link to CCCIR or SN tickets.