Versions Compared

Key

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

Return to the Table of Contents

...

Topics Covered in this section:

...

Expand
title8.7a: As a user of the DDSP, what browser do I need?

Organization’s need to ensure they use a supported internet browser version to be able to use the DDSP.

Supported Version(s) for Utilizing the DDSP

Note: Prior versions may work; however, they are not tested or guaranteed to work.

Internet Explorer

The DDSP will not support the use of Internet Explorer. 

Microsoft Edge

•Windows 10: Version 86.0.622.43 and above

•MacOS: Version 86.0.622.38 and above

Google Chrome

The Grammarly extension can cause some of the DDSP pages to display incorrectly and some page functionality to not work.  If you experience issues with the DDSP using Chrome and have this extension enabled; we recommend that you log out of the DDSP, disable Grammarly, and log back into the DDSP to determine if this extension is causing your issues. 

•Windows: Version 86.0.4240.75 and above

•MacOS: Version 86.0.4240.80 and above

Firefox

Version 81.0.2 and above

Firefox Extended Support Release: Version 78.3.1 and above

Safari(on Mac)

Version 14 and above

NOTE:  If you are not using one of the supported browser/versions on the computer(s) for use with the Joint Commission DDSP, please work with your internal information systems staff to download or upgrade to one of the browser/versions listed.  If you elect not to use a supported browser/version, you may not be able to log into the DDSP or use all of its functionality.  Browsers should be configured to enable JavaScript. 

Expand
title8.7b: As a user of the DDSP, what email domains does information come from?

The Joint Commission utilizes several resources to provide support to DDSP users. Verify with your internal IT department these emails have been added to a “safe-sender” list and not blocked or routed to junk/spam/clutter:

E-mails received by external customers HCOs are sent from email address:

“You have been invited to DDSP” come from: ddsp-manager@jointcommission.org

“Jira ticket has been opened/re-opened/closed” come from: support@jointcommission-ddsp.atlassian.net

“Send comment from inside JIRA to external customer” HCO” come from: jira@jointcommission-ddsp.atlassian.net

“Support outside the DDSP” come from: hcooryx@jointcommission.org

“Email communications” come from: @jointcommission.org

Expand
title8.8: What is the role of the Signature Authority for DDSP?
  • The Signature Authority is specific to the DDSP.

  • They are the first person to log onto the DDSP for a given organization.

  • The Signature Authority is the organization representative who has signing authority on behalf of their organization(s) and agrees to and accept the required legal forms related to the DDSP.

  • Once the platform has been initially accessed and the legal agreements signed, the Signature Authority is now simply a user on the Platform.

  • After initially accessing the DDSP, the Signature Authority can invite additional users to access their DDS workspace. These additional users may include other staff who can invite and manage other users.

  • The Signature Authority is not necessarily the same person who performs the data submission process. On-boarding is related to the agreement and acceptance of the required legal forms related to the DDSP.

  • Signature Authority's should on-board as early as possible to facilitate the review and acceptance of the legal forms.

  • If a Signature Authority changes roles or leaves the organization, the “signatory” role does not need to be reassigned, as they were the legal representative at the time the organization onboarded. If an organization does elect to add/change the signatory, be aware that no users can access the platform until the new signatory has accepted their invitation and signed off on use of the platform.

There are two or three distinct steps required to utilize the DDSP:

(1) organization onboarding (SeeQuestion/Answer 8.13 for information regarding onboarding);

(2) For eCQMs, (A) uploading QRDA I documents and (B) submitting eCQM data;

(3) For Chart-Abstracted Measures, entering and saving aggregate data.

NOTE: Each organization is responsible for all users who are invited and granted permissions on the DDSP per the legal agreements.

...

Expand
title8.14: Do we need to be onboarded to the Direct Data Submission Platform?

All organizations with ORYX Performance Measurement requirements are required to onboard to the DDSP. Joint Commission accredited organizations accredited as of CY2022 were onboarded to the new Joint Commission DDSP in July 2022.

After the initial onboarding to the new platform in 2022, we onboard newly accredited organizations quarterly. If a newly accredited organizations has not heard from us and needs to be onboarded to the DDSP, they should contact The Joint Commission via email to: hcooryx@jointcommission.org

Expand
title8.15: Who needs access to the DDSP?

All HCOs required to submit ORYX data for accreditation purposes need to onboard and access the DDSP. The Joint Commission initially onboards each organizations identified Signature Authority.
The organization is responsible for all users who are invited and granted permissions on the DDSP per the legal agreements signed by the organization.  The users granted permission could include organization staff, healthcare system staff and anyone else who is needed to assist in a successful submission of data for the organization (e.g., consultant, vendor).

...

Expand
title8.17: What is “Multi Factor Authentication”?

The DDSP utilizes “Multi Factor Authentication” as an extra layer of security beyond a password and username.

We strongly encourage organizations to work with their internal IT departments to install and understand the use of MFA applications.

If one MFA application is not working well for you, you may consider trying a different one, such as Authy for desktop, which does not require the use of a mobile phone or QR code scanner.

(See the MFA help topicDDSP Multi-Factor Authentication (MFA) for resources)

https://jointcommission-ddsp.atlassian.net/wiki/spaces/DCS/pages/24707087/Multi-Factor+Authentication+MFA

Expand
title8.18: How does a Signature Authority for multiple organizations complete the onboarding process?
  • The Signature Authority selects one of the onboarding emails they receive from the Joint Commission for their specific organization and login.

  • Signature Authority creates their login and password prior to onboarding the first organization.

  • After agreeing and accepting the required legal forms related to the DDSP for the selected organization, the Signature Authority should remain logged in. The purpose of remaining logged in is to simplify the process of onboarding the remaining organizations.

  • The Signature Authority selects each onboarding email (one for each organization) and agrees and accepts the required legal forms for each organization.

  • If the Signature Authority logs out of the DDSP, they are prompted to log back in using the login/password previously created when they begin onboarding their remaining organizations.

  • Signature Authority that completed the onboarding process for other organizations may log in to additional facilities by using their existing login and password, then accept remaining platform invitations for their other facilities.

  • Once onboarding of multiple organizations has been completed, the Signature Authority is able to navigate between these organizations to perform other activities without having to logout.

...

Continue to the next section: Direct Data Submission Platform - Technical

Return to the Table of Contents