Skip to main content

2025 REAL-WORLD TESTING RESULTS REPORT
§ 170.315(b)(1), (b)(10) and (g) (9)

PIMSY Platinum 9.0

Explore PIMSY Platinum 9.0’s 2025 Real-World Testing Plan (rwt), detailing how certified health IT features will be tested for interoperability and real-world functionality.

General Information

  • Plan Report ID Number:
  • Developer Name: Smoky Mountain Information Systems, LLC
  • Product Name(s): PIMSY Platinum
  • Version Number(s): 9.0
  • Certified Health IT: 15.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 for PIMSY Platinum 9.0 focused on evaluating compliance with ONC certification criteria §170.315 (b)(1), (b)(10), and (g)(9) to ensure real-world interoperability and system performance. The testing was conducted using the following methods:

  • Live Production Environment Testing – Validated system functionality in real-world usage scenarios.
  • Transaction Monitoring & Logging – Tracked success rates, errors, and response times for key interoperability functions.
  • Direct Messaging & Data Exchange Validation (§170.315 (b)(1)) – Ensured seamless C-CDA creation, sending, and receiving via Direct messaging for transitions of care.
  • Single Patient Export Testing (§170.315 (b)(10)) – Verified the system’s ability to generate and transmit complete patient EHI upon request.
  • FHIR API Functional Testing (§170.315 (g)(9)) – Confirmed patient access to full encounter summary data via third-party applications.

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

Care Settings

Care setting : Mental Health and 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

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/MetricDescription
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.

Associated Criterion(a): §170.315 (b)(10)

Relied Upon Software (if applicable): MeldRx ver. 2.0

Outcomes: During the Real World Testing for ONC §170.315 (b)(10) – Single Patient Electronic Health Information (EHI) Export, the system was successfully able to generate single patient export files upon request. While the total number of export requests during the 3-month period was lower than anticipated, the testing demonstrated that:

  • The single patient export functionality is fully operational and compliant with ONC requirements.
  • All export requests were processed successfully, with no errors or failures encountered.
  • The exported data included all required EHI elements in a structured format, ensuring data completeness and integrity.
  • Performance remained stable, and there were no delays or system failures when handling export requests.

Challenges Encountered (if applicable): N/A

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.

Associated Criterion(a): §170.315 (b)(1)

Relied Upon Software (if applicable): DataMotion Direct ver6.6

During the Real World Testing for ONC §170.315 (b)(1) – Transitions of Care, the system was successfully able to generate, send, and receive Consolidated Clinical Document Architecture (C-CDA) files via Direct messaging to and from third-party systems during transition of care events. While the total number of C-CDA exchanges during the test period was lower than anticipated, the testing demonstrated that:

  • The C-CDA generation and exchange functionality is fully operational and compliant with ONC requirements.
  • All C-CDA files were successfully created and transmitted, with no errors or failures encountered in the process.

This feature is available and regularly tested but It is just not widely used.

MEASURE 3:
§170.315 (g)(9)

Associated Criterion(a): §170.315 (g)(9)

Relied Upon Software (if applicable): MeldRx ver. 2.0

All Data Request (§170.315 (g)(9)) was fully operational, allowing patients to authenticate and use a third-party application on their own device to access their full encounter summary data. Patients were able to filter, view, use, and transmit their health information as per their needs. All authorized API requests were processed successfully, with no failures or timeouts. We noted that the total number of requests during the 3-month period was lower than anticipated

Associated Certification Criteria

Measurement/MetricAssociated Certification CriteriaRelied 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

Schedule of Key Milestones

Key MilestoneCare SettingCare Setting
Prepare the PIMSY Platinum application for Real world testing
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: 01/29/2026

The Real World Testing demonstrated that PIMSY Platinum effectively supports interoperability and data management in behavioral and mental health practice settings. Users efficiently managed external data, performed CQM-related tasks with ease, and utilized the API tool for seamless data exchange with third-party applications. No significant challenges were encountered during the testing period.