/
APHL Detor Post-Production Facility Addition Process

APHL Detor Post-Production Facility Addition Process

Owned by Emma Sudduth
Last updated: Mar 05, 2025 by riki.merrick
3 min read

With the use of Detor, post-production additions of facilities (e.g., hospitals) will require a coordinated effort between the PHL, APHL, and the applicable HCO. While APHL will provide the support necessary for adding a facility to Detor, it is the responsibility of the PHL to notify and coordinate these updates with APHL and its partner HCO.

The intended audience for this process document includes APHL’s Detor Team and both PHLs and HCOs that are in production with Detor.

Scope

The following process is relevant to a PHL that has an existing Detor solution with an HCO that needs to add a new sub-facility that is using the same EHR instance.

Note that this process is not relevant for establishing Detor with a new HCO partner. For those requests, please email detor@aphl.org.

APHL will review all post-production facility requests and reserves the right to notify the submitting PHL if their request exceeds the level-of-effort expected for a simple post-production update. Should this happen, the PHL, partner HCO, and APHL will collaborate to determine next steps for TA engagement.

Post-Production Update Process

Task

Responsible

Schedule

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 using the same EHR-system

    2. New facility name and location (city and state), note this information will be 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

Risks of Not Updating Detor for Facility Additions

Should a facility addition be implemented at the PHL and HCO without updating Detor, there are multiple warnings that could occur, and messages will not be correctly associated with the added facility.

 

Related content