Versions Compared

Key

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

...

...

...

...

...

...

...

...

...

...

...

...

Note that page is still in development. The preliminary sharing of this information is intended to benefit the ETOR initial implementers in preparation for their implementations, with the understanding that some information may change as our development evolves.

Monitoring Detor

In addition to the monitoring performed by APHL, your team will have a tool, DASH, available to monitor the routing of your organization’s test orders and results. Prior to productive use of ETOR Detor your team will test the use of DASH and be trained on the monitoring process.

The DASH user guide can be referenced here: INSERT LINK AIMS System Monitoring Dashboards User Guide (google.com)

Maintaining

...

Detor

Clinical Architecture’s Waypoint portal is the tool that will be used to manage the vocabulary service. This will need to be maintained and updated. During the implementation of ETORDetor, your team will receive training on this tool.

The Waypoint user guide can be referenced here: INSERT LINK Waypoint v22.3 User Guide (clinicalarchitecture.com)

If you require assistance in updating the vocabulary mapping, a request ticket can be submitted to AIMS support.

Requesting Support

Once you begin productive use of ETORDetor, you will be transitioned to AIMS support. This will ensure prompt and qualified support.

...

The below reflects the AIMS Production Support Severity Descriptions:

Severity

Description of Conditions

Catastrophic

The Service is down or almost entirely nonfunctional. Delivery of messages /documents to the final destination is greatly affected. Users are not able to use the Services and work practices are severely impacted. The condition may be due to the components of the APHL Platform being down, unreachable, or unusable.

Critical

The Service has considerably degraded performance. While the Service displays major faults or crashes, the users’ work can progress.

Medium

The Issue (1) affects the user and the problem has limited visibility or (2) is intermittent in nature and the user can still achieve full functionality on the platform.

Low

The Service is unaffected. The condition involves minor errors or bugs in the Service that do not impact on the business or the program function.

How to access Support

AIMS will provide portal access to the support desk for the purpose of reporting all issues and submitting requests. To access the support portal, use the following link: (to be provided). AIMS Service Desk - Jira Service Management (atlassian.net)

When submitting a ticket, be prepared to provide information related to:

  1. The relevant solutionservice: ETOR

  2. For incidents, the “impact” and “urgency” of the incident

  3. A summary Details of the incident or request

...

Updating Detor Test Panels

After going live with Detor, post-production changes to panels may be necessary. These include:

  1. Adding a new test to an in-production panel for a new disease

  2. Adding a new analyte to an in-production panel for an existing disease

  3. Adding a new order to an in-production domain

These changes to tests will require a coordinated effort between the PHL, APHL, and all impacted HCOs. APHL will provide the support necessary for panel adjustments to be added to Detor, but it is the responsibility of the PHL to notify and coordinate these updates with APHL and its partner HCO(s).

More information on updating Detor test panels and the process to be followed can be found here: APHL Detor PHL and HCO Post-Production Update Process - ETOR AIMS Implementations - Confluence