Page Comparison

Notify Impacted HCO(s) of Update

Include:

• Details on and requirements of update

• Timeline for update go-live at PHL

• Notification that APHL Support will be requested, and additional information will be shared

• Impact if HCO(s) is not prepared by production date

PHL

As soon as PHL is aware of update

Request APHL Support via Help Desk

Submit a ticket and include the following information:

1. The relevant service: ETOR

2. The relevant panel (if your PHL has multiple panels in-production)

3. Details of the panel adjustment(s), including:

   1. Type of adjustment

      1. New analyte for a new disease,

      2. New analyte for an existing disease, or

      3. New AOE/ASC questions (if appropriate)

   2. Name of test

   3. Possible values for test results

   4. The status of the adjustment in your LIMS

      1. Whether it's coded into the system

      2. Whether it’s programmed to output

   5. The date the test will be implemented at the PHL

4. Any relevant documentation, such as a compendium

PHL

As soon as PHL is aware of update and can provide ticket details, ideally no less than 90 days before production update

Review and Respond to Support Ticket

• Assign ticket and add appropriate participants

• Review ticket details and request any additional details needed to scope and schedule work

• Notify PHL if the update cannot be handled via this simple process and requires more significant TA engagement

APHL

Within 1 week of ticket receipt

Provide Schedule and Communication Details to PHL

Provide PHL:

• A target date for updated mapping to be complete in Detor (i.e., when mapping will have been configured in Detor’s ONBOARD environment and is ready for testing with partners)

• The value(s) the partner HCO(s) should expect for the panel adjustment

• A reminder to let the partner HCO(s) know what will happen if they don’t update their EHR by the implementation date

APHL

Within 1 week of receiving all required details from PHL

Communicate APHL Support Information to Impacted HCO(s) and Coordinate Testing

Include:

• APHL’s target date for updated mapping to be complete in Detor (i.e., when mapping will have been configured in Detor’s ONBOARD environment and is ready for testing with partners)

• Potential testing windows (after APHL’s target date for updated mapping to be complete in Detor) for PHL/HCO(s) update validation

• The value(s) the partner HCO(s) should expect for the panel adjustment

• A reminder to let the partner HCO(s) know what will happen if they don’t update their EHR by the implementation date

PHL

As soon as details are received from APHL

Update Detor ONBOARD Environment to Support Update

Update Detor and provide update within ticket to reflect completion and readiness for PHL and HCO testing.

Note that addition of new tests will require sign off in Symedical Waypoint, so the approprate folks on the PHL and HCO side need to be included in the notifications

APHL

Depends on update complexity; expected timeline will have been communicated by APHL via ticket

Update LIMS TEST Environment to Support Update

PHL

Depends on update complexity; expected timeline will have been communicated by PHL via ticket

Update EHR TEST Environment to Support Update

HCO(s)

Depends on update complexity; expected timeline will have been communicated by HCO to PHL

PHL and HCO Testing via Detor ONBOARD

PHL should coordinate and monitor all testing with HCOs. If issues arise that are related to Detor processing, a service ticket should be submitted.

PHL

Notify APHL of Confirmed Production Date

This update should be provided within the original ticket.

PHL

No less than 2 weeks before the planned production use date

Update Detor PRODUCTION Environment to Support Update

Update Detor and provide update within ticket to reflect completion and readiness for PHL and HCO go-live.

APHL

Before the confirmed production use date