PSOs and vendors submit patient safety concern data to the PSOPPC. Analysis of this data is intended to facilitate the development and adoption of interventions and solutions to improve patient safety. Patient safety data is aggregated and made non-identifiable by the PSOPPC for transmission to the Network of Patient Safety Databases (NPSD).
Data Submission overview for Common Formats for Event Reporting - Community Pharmacy Version 1.0 (CFER-CP V1.0) , Common Formats for Event Reporting - Hospital Version 1.2 (CFER-H V1.2) and Common Formats for Event Reporting - Hospital Version 2.0 (CFER-H V2.0) describe the steps necessary for a Patient Safety Organization (PSO) or vendor to submit patient safety concerns to the PSOPPC and to the Network of Patient Safety Databases (NPSD).
PSE Data Submission Process Overview Posted on: 05/14/2014, 201 KB
The PSOPPC compiled a list of common questions associated with the patient safety data submission process. The following document is updated as additional questions are received.
Data Submission FAQs Posted on: 06/18/2014, 306 KB
The PSOPPC is responsible for the non-identification and aggregation of data received from PSOs. To assist in the creation of non-identifiable data, PSOs assign a unique provider identifier to each healthcare provider contracting with the PSO.
The PSO-Assigned Provider Identifier Code (Provider ID Code) serves as a surrogate Provider ID Code. When the PSO assigns a surrogate ID code to the provider, the identity of the submitting provider is not revealed to the PSOPPC, thus providing anonymity to the healthcare providers. The Educational Brief Issue 40 - Recommended Practices for PSOs Assigning Pseudo Provider IDs for Data Submission to the PSOPPC provides guidance on creating Pseudo Provider ID codes.
It is imperative that the same PSO-Assigned Provider ID Code be used for all files submitted to the PSOPPC for that particular provider. Using the same PSO-Assigned Provider ID Code allows for data aggregation by the provider.
Before a PSO can submit Patient Safety Work Product to the PSOPPC, the PSO must sign a PSO Data Use Agreement. For PSOs choosing to submit patient safety information, an agreement must be executed to specify the respective rights and responsibilities of the PSO and the PSOPPC. The agreement specifies the types of patient safety information, format of data elements, explains how the data may be used, which elements will be transferred to the NPSD, how long the PSOPPC may use the data, and how the data will be protected.
Data Use Agreement Posted on: 04/03/2015, 310 KB
A PSO may designate a PSO Vendor to act on their behalf for certain functionalities on the PSOPPC website such as submitting patient safety data. A PSO Vendor must register with the PSOPPC in order to submit patient safety data on behalf of a PSO. PSO Vendors may complete the Vendor Organization Registration Form prior to contracting with any PSOs.
Vendor Organization Registration Form Posted on: 05/12/2014, 34 KB
Implementation Guides provide valuable information on the specifications for submitting data from PSOs to the PSOPPC.
The Resources Workbooks complement the Implementation Guides and provide information that will assist with the development of a Common Formats Patient Safety Report CDA file. This document contains information on the validation rules that will be applied to the Common Formats data elements and the associated answer values submitted to the PSOPPC.
The Common Formats Flow Charts provide the data elements and associated answer values (where applicable) recommended for collection based on the report type and event category associated with the patient safety data report. The Common Formats Flow Charts also outline the path for a complete patient safety data report.
For more information regarding the Implementation Guides, Resources Workbooks, and the Common Formats Flow Charts, please refer to the following pages:
A submitting organization must have a signed DUA, and the user assigned to submit patient safety data to the PSOPPC must have a Level 3 User Account with the PSOPPC. To obtain a Level 3 account, please visit Account Setup page.
Helpful Hints for submitting file(s) to the PSOPPC:
With the help of an intuitive Web Interface, authorized PSOPPC users can upload either CDA XML or Alternate Data Submission files to the PSOPPC.
The PSOPPC has also implemented a SFTP solution as an alternative to the Web interface for data submission. Submitting data via the SFTP system will require the same prerequisites as submission through the PSOPPC website; additionally, users will need to register for an SFTP account by contacting the PSOPPC Help Desk.
For detailed instructions on how to submit data via SFTP, please refer to the PSOPPC SFTP Data Submission User's Manual.
PSOPPC SFTP Data Submission Users Manual Posted on: 08/28/2015, 696 KB
The PSOPPC accepts patient safety data in XML format that conforms to the Health Level Seven (HL7) Clinical Document Architecture, Release 2.0 (CDA R2) standard.
The Alternate Data Submission file format enables PSOs and vendors to submit patient safety data in basic XML or Delimiter-separated values (DSV) format. It is an alternative to the current CDA XML submission requirement.
For detailed instructions on how to implement and use the Alternate Data Submission process, please refer to the following user guides and Sample Files:
CFER-H_V2.0a_Alternate_Data_Submission_Users_Guide Posted on: 08/03/2018, 247 KB
CFER-H_V1.2_Alternate_Data_Submission_Users_Guide Posted on: 04/20/2018, 568 KB
CFER-CP_V1.0_Alternate_Data_Submission_Users_Guide Posted on: 04/20/2018, 425 KB
CFER-H_V2.0a_Alternate_Data_Submission_File_Samples Posted on: 08/03/2018, 13 KB
CFER-H_V1.2_Alternate_Data_Submission_File_Samples Posted on: 12/15/2017, 19 KB
CFER-CP_V1.0_Alternate_Data_Submission_File_Samples Posted on: 04/27/2018, 4 KB
Once patient safety data file(s) are successfully submitted to the PSOPPC, the user submitting the files receives an email detailing the results. It is important to review these results. Only files with a status of "Accepted" are made non-identifiable and sent to the NPSD. Users can also review results via the Submission Management reports on the PSOPPC website or utilize the Web Service, as detailed below. Furthermore, users are encouraged to run the Common Formats Aggregate Report to confirm the data submitted accurately reflects what they received from providers.
The Submission Management Summary Report displays summary file processing information for submitted files. This is the report used to determine whether a file was "Accepted" or "Rejected".
The Submission Management Detail Report provides information on the specific errors that occurred in a "Rejected" file, including the message code, description, and type.
The Common Formats Data Submission Error Messages document provides all possible error messages for patient safety data submissions. The validation rule that failed is presented alongside the error message to assist PSOs in the revisions of the file. There are Error Messages documents for each Common Format available for reporting, which can be found under the Technical Specifications section.
The PSOs are encouraged to generate and review the appropriate Aggregate Reports following the "Test" submission of their data to ensure the data reported to the PSOPPC accurately reflects the data received from providers. As the data is passed from providers to the PSO and then to the PSOPPC, data transformation and/or mapping issues may occur. This report provides PSOs and vendors the opportunity to perform validation of their data. The following document provides suggestions for evaluating the data and may be used as a starting point for the PSOs to develop their own method for reviewing and interpreting the data submitted by the providers.
How to Use the Aggregate Report Posted on: 05/13/2014, 590 KB
The Web Service provides PSOs and vendors the ability to query the submission status, amongst other details, of their patient safety concern data submissions. In addition to an existing Level 3 User Account, an additional username and password will be required to access the Web Service.
The following document provides information on how to utilize the Web Service:
PSOPPC Web Service Users Manual Posted on: 02/25/2017, 1,098 KB
Back To Top