Governance approval process for custom integrations
Teams often request custom W2H integrations with Epic. Common examples include:
SDE write back for discrete patent data to go from W2H → Epic
API access to facilitate new functionality, like using PlaceOrdersUsingTemplate API to pend orders for patients
Clinical leads for these projects should follow the steps below, with help from W2H, to gain access and resourcing to implement these custom integrations. W2H should not drive these requests or present them at governance committees unless CHTI has designated the project as a priority for our portfolio. We’ve also heard from IS that they want the clinical champions to drive these requests, not W2H.
Steps required:
Clinical lead brings the request to their local governance group. See the Enterprise and Specialty Review Council lists for additional information. Most commonly, teams we work with go to: Department of Medicine, Cardiology, Population Health, or various ‘ambulatory’ groups. Each group has its own cadence and owner, but often the groups meet monthly.
Local governance group approves/denies the request or suggests whether other additional clinical governance groups need to approve.
Clinical lead brings the request to IS governance group. See the Technical Expert Review list for additional information. Most commonly, requests are brought to the API/FHIR governance committee led by Gordon Tait. The technical review is to ensure that the solution is the appropriate solution for the request.
Following IS governance approval, W2H will receive information about approval and plans for testing before the requests can be moved to production. Contact @Michael Josephs to schedule developer time/resources to complete this testing.
Additional governance owners in case of questions:
