Versions Compared

Version Old Version 3 New Version 4
Changes made by

riki.merrick

Emma Sudduth

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Task

Responsible

Schedule

1

Request APHL Support via Help Desk

Submit a ticket and include the following information:

  1. The relevant service: ETOR

  2. Details of the facility update:

    1. In-production HCO adding a facility

    2. New facility name and location (city and state), note that the nomenclature provided is how it this information will be displayed used in DASH (ST.FacilityName.City)

    3. New facility unique identifier that will be included in message

    4. New facility NPI

    5. Confirmation that new facility messages will be sent/received via the existing HCO endpoint

    6. Requested date for facility addition

    7. Contact phone number

PHL

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

2

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

3

Provide Schedule and Communication Details to PHL via Support Ticket

Provide PHL:

  • A target date for updated mapping to be complete in Detor ONBOARD environment so that testing can begin

  • A reminder to ensure PHL’s and HCO’s testing environments are updated and ready to test facility addition

APHL

Within 1 week of receiving all required details from PHL

4

Communicate APHL Support Information to Impacted HCO and Coordinate Testing

Include:

  • APHL’s target date for testing availability

  • Potential testing windows

PHL

As soon as details are received from APHL

5

Update Detor ONBOARD Environment to Support Update

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

APHL

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

6

Update LIMS TEST Environment to Support Update

PHL

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

7

Update EHR TEST Environment to Support Update

HCO(s)

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

8

PHL and HCO Testing via Detor ONBOARD

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

If CLIA validation is necessary, the PHL should coordinate and document relevant testing.

PHL

9

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

10

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.

Following the Detor production update, the support request ticket will be closed. Any issues that arise once available in Detor production should be submitted as incident tickets.

APHL

Before the confirmed production use date

...