• Preliminary
    Call
  • Overview
  • Data Mapping
    & Workflow
  • Quality Program
    Review
  • Abstractor Credentialing
  • System
    Orientation
  • Post Orientation Validation
  • First
    Abstraction
  • Steady State
    Abstraction

MILESTONE

04

Abstractor Credentialing & Validation

Estimated time commitment: variable

After our QIS team is provisioned credentials, our IT team will validate the ability of each team member to access the appropriate data. This process can take varying levels of time. However, should this process reveal errors or complication, our IT team will collaborate with your IT team member.

Stakeholders include but are not limited to: Project Coordinator; IT member; Quality Administrator

Before Abstractor Validation Efforts: A Few To Do

  • Double-check the credentials.
    Avoid errors in validation by reviewing spelling and related information system information prior to sending the credential information on to your Q‑Centrix project manager.
  • Communicate the priority of validation to your IT team member.
    After provisioning credentials, your IT team member may consider his or her involvement complete. However, validation can reveal some critical issues with our team’s access that require attention by your IT team. In order to avoid significant delays in the implementation process, inform your IT team member of the importance of validation.

Troubleshooting Remote Access Delays

When we experience delays in obtaining credentials for our team to access information systems, we’ve found that there’s typically only one culprit — a misunderstanding. In fact, when speaking with our existing customers, several have identified two key types of misunderstandings that once resulted in delayed access: security and priority. To avoid any delays in access, we recommend proactively addressing these topics with your IT team member.

Our security measures

Our model and workflow are built around maintaining the utmost data security. See how we outline the data flow in a read-only write-only environment as well as a data feed environment.

The financial implications of delay

No organization ever wants to delay an implementation. In some cases, a delay may be the only option; more often than not it is the result of competing priorities. Find out why we think quality should always win.

You've finished this milestone!

Go to the next step