2025 Real-World Test Plan
PIMSY Platinum 9.0
General Information
- Plan Report ID Number:
- Developer Name: Smoky Mountain Information Systems, LLC
- Product Name(s): PIMSY Platinum
- Version Number(s): 0
- Certified Health IT: 04.04.2342.Pims.09.00.1.231204
- Developer Real World Testing Page URL: https://pimsyehr.com/mandatorydisclosures/RWT
Justification for Real World Testing approach
The Real-World Testing plan will focus on using PIMSY Platinum is to demonstrate interoperability and functionality of certified health IT in real world settings and scenarios. The initial plan was based ONC’s published standards (https://www.healthit.gov/topic/certification-ehrs/real-world-testing).
This report outlines PIMSY’s plan to measure the real-world use of interoperability features for the year 2025 for their PIMSY PLATINUM 9.0 Certified health IT. The certification criteria to be observed in this plan include § 170.315(b)(1), (b)(10) and (g) (9)
We will test the §170.315 (b)(10) criteria separately. The testing of (b)(10) will cover both single and bulk data requests for all criteria.
Standards Updates (including standards version advancement process (svap) and United States core data for interoperability (USCDI)
Standard (and version) | NA |
Updated certification criteria and associated product | NA |
Health IT Module CHPL ID | NA |
Method used for standard update | NA |
Date of ONC-ACB notification | NA |
Date of customer notification | NA |
Conformance measure | NA |
Measures used in overall approach
The Measure/Metrics and the Descriptions listed below will apply to the individually tested §170.315 (b)(10) and the simultaneous and seamless use of the functionality of certified measures §170.315 (b)(1) and §170.315 (g)(9)The RWT be witnessed via a Zoom/M S Teams session with the participants using a production environment and real patient data. Upon completion, we will observe the successful conformance of the certified technology to be able to Export the EHI data for (b)(10), (b)(1) and (g)(9)
| Measurement/Metric | Description |
|---|---|
MEASURE 1: §170.315 (b)(10) Export USCDIv1 clinical data for a population of patients for use in a different health information technology product or a third-party system. This export can be used for many purposes, including data portability when a physician practice switches to a new EHR platform. | We chose to concentrate on the aspects of this criterion that would: 1) Demonstrate an EHR’s ability to export batches of patient data in a straightforward fashion 2) Facilitate interoperability by providing the exported data in the form of valid C-CDA files that conform to the HL7 standards as described in the HL7 Implementation Guide for CDA® Release 2: Consolidated CDA Templates for Clinical Notes (US Realm). Additionally, it includes a publicly accessible hyperlink to the export’s format. |
MEASURE 2: §170.315 (b)(1) This measure is tracking and counting how many C-CDAs are created and successfully sent/received to or from the EHR Module to a 3rd party via Direct messaging during a transition of care event over the course of a given interval. | This measure is tracking and counting how many C-CDAs are created and successfully sent from the EHR Module to a 3rd party via Direct messaging during a transition of care event over the course of a given interval. The measurement will produce numeric results over a given interval. We will utilize various reports and audit logs, including Automated Measure (315.g.2) reports, to determine our measure count. A successful measure increment indicates compliance to the underlying ONC criteria. It will show that the EHR can create the C-CDA patient summary record, including record required clinical data elements. In sending the C-CDA patient summary record, the EHR will demonstrate ability to confirm successful interoperability of an exchanged patient record with a 3rd party, including support for Direct Edge protocol in connecting to a HISP (DataMotion). Successfully completing this measure also implies users have a general understanding of the EHR functional operations for this EHR Module and an overall support for the user experience while not completing this measure may indicate lack of understanding or possibly lack of use or need for this functionality. We will use the measure count to establish a historic baseline of expected interoperability use so it can be used in subsequent real-world testing efforts. |
MEASURE 3: §170.315 (g)(9) | A patient will be enabled to present their authenticated credentials to use a 3rd-party application running on a patient-owned device to access their full encounter summary data. They will have the ability to filter and view, use and or transmit their information as they see fit. This will meet § 170.315 (g)(9) criteria. |
Associated Certification Criteria
| Measurement/Metric | Associated Certification Criteria | Relied Upon Software |
|---|---|---|
MEASURE 1: | §170.315 (b)(10) | MeldRx ver. 2.0 |
MEASURE 2: | §170.315 (b)(1) | DataMotion Direct ver6.6 |
MEASURE 3: | §170.315 (g)(9) | MeldRx ver. 2.0 |
Justification for Selected Measurement/Metric
| Measurement/Metric | Justification and expected outcomes |
|---|---|
MEASURE 1: §170.315 (b)(10) Count of single patient export files created during a 3-month timeframe. This demonstrates the ability to export single patient files containing all their EHI. | Count of single patient export files created during a 3-month timeframe. This demonstrates the ability to export single patient files containing all their EHI. This metric will also provide information on the demand for this capability. |
MEASURE 2: §170.315 (b)(1) This measure is tracking and counting how many C-CDAs are created and successfully sent/received to or from the EHR Module to a 3rd party via Direct messaging during a transition of care event over the course of a given interval. | The Real-World Testing will demonstrate that the clinician can send/receive C-CDA R2.1 CCDA Document (USCDI v1) payload type in the designated setting. Using the Edge Protocol SMTP protocol. Both Referral Notes and Encounter Summaries will be evaluated. The received document will be evaluated for the ability to:
A 95% completion success rate is expected within the established normal time (usually under 20 seconds) to complete each function. As detailed in this plan under the “Schedule of Key Milestones” section, each measure/metric will be tested at least once a quarter with our clinician RWT groups to ensure the expected outcomes are reliably attained. |
MEASURE 3: §170.315 (g)(9) This is a measure to determine how many different systems or applications are connecting to our EHR via the API. We will look over the course of a minimum of six (6) months to gauge registered applications and active use. | This measure will determine how many 3rd party systems or applications are integrated and using the EHR’s FHIR API interface. This measure will allow us to verify our certified API is working with 3rd party applications to access USCDI patient data. This measurement will validate proper integration of our relied upon software MeldRx (Version 2.0) Interface Engine for connectivity to our FHIR server. PIMSY Platinum will demonstrate the functionality to respond to requests for patient data for all of the data categories specified in the USCDIv1 Data Set at one time and return such data (according to the specified standards, where applicable) in a summary record formatted according to the standard adopted C-CDA standard.
Success rate |
Care Setting(s)
| Measurement/Metric | Justification |
|---|---|
• Mental Health • Behavioral Health | PIMSY Platinum is currently used by behavioral health staff and providers in the Ambulatory setting of Mental and Behavioral Health. This test plan will demonstrate that the overall functionality is the same for each provider. We will get feedback from the actual users. We will confirm that the EHR accommodates the specific workflow of for this point-of service. We will be conducting the Real-World Testing with clinicians delivering care to patients. The ability to complete all measures successfully with these clinicians will be documented through observation of the completed tasks. Deviations from the designed process, if any, will be noted and addressed |
Schedule of Key Milestones
| Key Milestone | Care Setting | Care Setting |
|---|---|---|
Prepare the PIMSY Platinum application for | Ambulatory Setting | December 2024 |
Identify the user practices that will participate in the test plan | Ambulatory Setting | December 2024 & January 2025 |
Confirm that the Real-World Test Plan participants can log into their accounts | Ambulatory Setting | January 2025 |
Follow up with the Real-World Test Plan participants on a regular basis (minimum, once a quarter) to obtain feedback on their progress and or if there are any issues to address | Ambulatory Setting | Quarterly 2025 |
End the Real-World Test to coincide with the end of the MIPS 2025 Performance Year. | Ambulatory Setting | January 2026 |
Real-World Test analysis and generation of the report | Ambulatory Setting | January 2026 |
Submit Real-World Test Report to ACB before established deadline | Ambulatory Setting | January 2026 |
Attestation
This Real-World Testing plan is complete with all required elements, including measures that address all certification criteria and care settings. All information in this plan is up to date and fully addresses the health IT developer’s Real-World Testing requirements.
Authorized Representative Name: Allison Sellars
Authorized Representative Email: allison@pimsyehr.com
Authorized Representative Phone: 877-334-8512
Authorized Representative Signature: : /Allison Sellars/
Date: 10/30/2024