2024 Real World Testing: ChartLogic

ChartLogic EHR

GENERAL INFORMATION

Developer Name: ChartLogic, a Division of Medsphere Systems Corporation

Plan Report ID Number: 20231027chl

Product Name(s):

  • ChartLogic EHR
  • ChartLogic EHR Classic

Version Number(s):

  • ChartLogic EHR v. 1
  • ChartLogic EHR Classic v. 9

Product List (CHPL) ID(s):

  • ChartLogic EHR – 15.05.05.1223.CEHR.02.01.1.230103
  • ChartLogic EHR Classic – 15.05.05.1223.CHRT.02.01.1.221222

ONC-ACB Certification ID:

  • ChartLogic EHR – 15.05.05.1223.CEHR.02.01.1.230103
  • ChartLogic EHR Classic – 15.05.05.1223.CHRT.02.01.1.221222

Developer Real World Testing Page URL:

https://www.medsphere.com/certifications/RealWorldTesting/ChartLogic

JUSTIFICATION FOR REAL WORLD TESTING APPROACH

At this time, ChartLogic is only utilized within Ambulatory Practices. Therefore, the Real World Testing plan will apply to this care setting. We feel it is best to test functionality as a whole workflow rather than by individual measure as this is how it is utilized in the real world. Our Real World Testing approach will consist of three main components, Electronic exchange of information for Care Coordination and Patient Engagement, Population Health, and Application Programming Interfaces.

Electronic exchange of information for Care Coordination and Patient Engagement

ChartLogic has developed functionality and created a best practice workflow around sending, receiving, reconciling, and exporting electronic health information. This workflow will allow us to test several certification criteria simultaneously. All criteria involving the Consolidated Clinical Documentation Architecture (C-CDA) documents will be tested, including 170.315(b)(1) Transitions of Care, 170.315(b)(2) Clinical Information Reconciliation and Incorporation, 170.315 (e)(1) View, Download and Transmit (ChartLogic v1 only) and 170.315(h)(1) Direct Project.

Population Health

As the product is targeted for ambulatory practices in which a wide variety of patient ailments are seen and across multiple populations, we find it important to be able to communicate to public health registries as well as immunization registries.

Being able to efficiently transmit certain clinical information to external specialized registries is foundational to population health. This plan will also incorporate the testing of 170.315(f)(1) Transmission to immunization registries, and 170.315(f)(2) Transmission to public health agencies – syndromic surveillance and 170.315(f)(5) Transmission to public health agencies – electronic case reports.

Application Programming Interfaces

ChartLogic has also developed Application Programming Interfaces to enable ways for our providers to communicate and transfer data to external systems. ChartLogic also will test multiple measures simultaneously around the criteria involving Application programming interfaces, including 170.315(g)(7) Application access- patient selection, and for ChartLogic v1 only 170.315(g)(9) Application access – all data request.

STANDARDS UPDATES (INCLUDING STANDARDS VERSION ADVANCEMENT PROCESS (SVAP) AND UNITED STATES CORE DATA FOR INTEROPERABILITY (USCDI))

This product utilizes all standards associated with the 2015 Cures Update methods.

Standard (and version)USCDI v1
Updated certification criteria and associated productb1, b2, and f5 for both ChartLogic v1 and v9 e1, g9 apply to ChartLogic v1 only.
CHPL Product Number15.05.05.1223.CEHR.02.01.1.230103, 15.05.05.1223.CHRT.02.01.1.221222
Method used for standard updateCURES update
Date of ONC ACB notification12/12/2022
Date of customer notification (SVAP only)Not Applicable
Conformance measureMeasure 1 for b1, b2, e1, Measure 2 for f5 Measure 3 for g9
USCDI updated certification criteria (and USCDI version)b1, b2, e1, f5, g9—USCDI v1

MEASURES USED IN OVERALL APPROACH

The following outlines our measures that have been identified to best demonstrate how our product is in and maintains conformance to multiple certification criteria.

Electronic exchange of information for Care Coordination and Patient Engagement

Measure 1 (Care Coordination Exchange Thresholds and Mechanisms)

As part of the Real World Testing requirements for 170.315(b)(1) Transitions of Care, 170.315(b)(2) Clinical Information Reconciliation and Incorporation, 170.315 (e)(1) View, Download, and Transmit (ChartLogic v1 only) and 170.315(h)(1) Direct Project, this measure will assess the sending and receiving of CCD-A documents, reconciling information received through the CCD-A, the methods of transmission for information shared between providers.

Metric 1 – This metric will determine the thresholds of the types of transport mechanism used to share transitions of care documents and EHI, as well as the success rate of transmission. Associated certification criteria for the electronic exchange of information for Care Coordination and Patient Engagement in the ambulatory care setting include:

Certification CriteriaAssociated CriteriaRelied Upon Software
170.315(b)(1) Transitions of CareSend Transition of care/referral summariesSurescripts Clinical Direct Messaging
Receive transition of care/referral summaries
170.315(b)(2) Clinical Information Reconciliation and incorporationReconcile transition of care summaryN/A
170.315(h)(1) Direct ProjectTransmit summary using one of the methods of direct exchangeSurescripts Clinical Direct Messaging
170.315(e)(1) View, download and transmit (ChartLogic V1 only)Download ambulatory summary or inpatient summary using CCD TemplateN/A
Download of transition of care/referral summaries
Transmit to third party

Rationale: The system includes three functionalities of interest transmitting, receiving and reconciling electronic health information. These transitions of care documents can be shared using various transmission methods such as XDM processing, direct, SMTP, while other documents can be shared through the patient portal either encrypted or unencrypted. This metric will provide ChartLogic with information on the types of transmissions that are used and the frequency of the individual usages. We feel that these findings could help us determine which methods are the most advantageous to our target base and also help us identify those best practices that we can target those providers with low thresholds in order to reach out to them and provide them logic as to how to increase utilization. For ChartLogic V 1 only, we also feel that the metrics captured in test approach 2 will help us identify the usage of download and transmit functions by patients.

Test Approach 1: De-identifiable data from system logs, will be extracted in order to produce analytic reports that will be reviewed to determine thresholds of transmission used by the providers for transmitting and receiving transitions of care.

Expected Outcome(s): It is anticipated that providers and patients will be able to share their electronic health information with no limitations and in compliance with the certification criteria, including the technical standards and vocabulary code sets.

Transmission errors will be tracked and trended over time and trended to determine utilization rates.

Test Approach 2: Information of actions of download and transmit will be extracted from system logs to determine the success rate of patients downloading and transmitting documents.

Expected Outcome: It is expected that patients will be able to share their information using the transmission methods provided with no limitations. The success/failure of the events will be logged and reviewed over time.

Measure 2 (Transmission of HL7 messages)

This measure will capture the error rates of HL7 messages being transmitted. Specifically, we will extract the VXU message types to analyze error rates related to Immunization registries and extract ADT messages to analyze error rates for public health agencies. We will also extract the entries that indicate when an electronic case report was generated to determine the utilization rate of generating electronic case reports.

Certification CriteriaAssociated CriteriaRelied Upon Software
170.315(f)(1) Transmission to Immunization RegistriesTransmit VXU message to external entityNotepad++ (ChartLogic v1 only)
170.315(f)(2) Transmission to Public Health Agencies – Syndromic SurveillanceTransmit ADT message to public health agency.N/A
170.315(f)(5) Transmission to Public Health Agencies – Electronic Case ReportsNumber of electronic case reports generatedN/A

Rationale: ChartLogic allows clinicians the ability to generate and transmit certain information to external entities using HL7 standards. These message types are transmitted through an HL7 engine and logged in the system. When immunization data or communicable disease data is captured within the system, these data elements are parsed into an HL7 message and transmitted to the respective external entity. This will provide an analytical view of the success rates of transmission.

ChartLogic also allows users to generate electronic case reports based on consumption of a list of trigger codes.

Test Approach 1: System logs will be used to extract certain message types related to immunization and syndromic surveillance activities. Success rates of VXU message types being delivered to immunization registries as well as ADT messages being delivered to public health agencies will be reviewed and trended. System logs will also be used to extract a total number in which electronic case reports were generated.

Expected Outcome(s): It is expected that clients will be able to transmit HL7 messages without limitations and in compliance with the certification criteria, including the technical standards and vocabulary code sets. We do anticipate some clients will experience some delay on first attempt due to network connectivity so we anticipate that 90% of messages will be successfully transmitted and the 10% error rate accounts for issues with network. It is also expected that clients will be able to generate electronic case reports without error. Tracking the number of times electronic case reports are generated will identify usability metrics within our client base.

Measure 3 (API Requests)

This measure will capture the volume of API transactions across the measurement period.

Certification CriteriaAssociated CriteriaRelied Upon Software
170.315(g)(7) Application Access- patient selection Immunization RegistriesAPI query for patientN/A
170.315(g)(9) Application Access – all data request – ChartLogic v1 onlyAPI query for all data related to patientN/A

Rationale: ChartLogic has developed API’s that can be used by external entities. These API’s can be used to ping the system in order to retrieve certain information based on a query for a single patient, requesting specific data categories for that patient or requesting all data for the selected patient.

Test Approach 1: (in the event we have an external system using the API’s)System

logs will be used to capture the success rate of API transactions over time.

Expected Outcome(s): It is expected that external entities will be able to connect to the ChartLogic system without error using these API’s without limitation and in compliance with the certification criteria, including the technical standards and vocabulary code sets. These successful transaction thresholds will be used to demonstrate the utilization of the API in the real world over the testing year. The numbers reflected in the all data request will only come from the ChartLogic v1 product.

Test Approach 2: (in the event we do not have any external system using the API’s). Quarterly tests will be done in a test environment to ensure the API’s are functionable. This will be done by using a test system to ping the host application for each level of access and the success/failure of the ping will be captured. This test will be done quarterly.

Expected Outcome(s): It is expected that the test system will be able to connect to the ChartLogic system without error using these API’s without limitation and in compliance with the certification criteria, including the technical standards and vocabulary code sets. We anticipate that the test system will be able to perform patient/data requests successfully during each quarter. At the end of the testing year, we anticipate to have 4 successful events for each of the request types.

Care Setting(s)

ChartLogic is only marketed to the ambulatory practice setting, therefore, only ambulatory practices will be used for Real World Testing.

SCHEDULE OF KEY MILESTONES

Key MilestoneDate/Timeframe
Begin collection of data laid out by planMarch 2024
Data Collection and ReviewQuarterly
End of Real World Testing for all measures.December, 2024
Final data review and analytics, create results reportJanuary 2025
Submit Real World Testing Results Report to ACBJanuary 2025

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: Nicki Anderson, Director, Compliance
Authorized Representative Email: nicki.anderson@medsphere.com
Authorized Representative Phone:      760.979.6531
Authorized Representative Signature:               Nicki Anderson
Date:  October 26, 2023

ChartLogic Patient Portal

GENERAL INFORMATION

Developer Name: ChartLogic, a Division of Medsphere Systems Corporation

Plan Report ID Number: RWTP-001079

Product Name(s): ChartLogic Patient Portal

Version Number(s): ChartLogic Patient Portal v. 9

Product List (CHPL) ID(s):

  • ChartLogic Patient Portal – 15.04.04.1223.Char.09.00.1.170814

ONC-ACB Certification ID:

  • ChartLogic Patient Portal – 15.04.04.1223.Char.09.0.1.170814

Developer Real World Testing Page URL:

https://www.medsphere.com/certifications/RealWorldTesting/ChartLogic

JUSTIFICATION FOR REAL WORLD TESTING APPROACH

At this time, ChartLogic Patient Portal is only utilized within Ambulatory Practices using ChartLogic. Therefore, the Real World Testing plan will apply to this care setting.

Electronic exchange of information for Patient Engagement

ChartLogic Patient Portal has developed functionality to enable patients to view, download and transmit electronic health information. The best practice workflow will allow us to test the utilization of this feature as well as the how the patients are transmitting the data. This plan addresses the criteria involving the Consolidated Clinical Documentation Architecture (C-CDA) 170.315e(1) View, download, and transmit to 3rd party,

STANDARDS UPDATES (INCLUDING STANDARDS VERSION ADVANCEMENT PROCESS (SVAP) AND UNITED STATES CORE DATA FOR INTEROPERABILITY (USCDI))

This product utilizes all standards associated with the 2015 Cures Update methods.

Standard (and version)USCDI v1
Updated certification criteria and associated product e1
CHPL Product Number15.04.04.1223.Char.09.00.1.170814
Method used for standard updateCURES update
Date of ONC ACB notification12/12/2022
Date of customer notification (SVAP only)Not Applicable
Conformance measureMeasure 1, e1
USCDI updated certification criteria (and USCDI version)e1, USCDI v1

MEASURES USED IN OVERALL APPROACH

The following outlines our measures that have been identified to best demonstrate how our product is in and maintains conformance to for 170.315e(1) View, download, and transmit to 3rd party.

Electronic exchange of information for Patient Engagement

Measure 1 (Care Coordination Exchange Thresholds and Mechanisms)

As part of the Real World Testing requirements for 170.315e(1) View, download, and transmit to 3rd party, this measure will assess the utilization of downloading and transmitting CCD-A documents.

Certification CriteriaAssociated CriteriaRelied Upon Software
170.315(e)(1) View, download and transmitDownload ambulatory summary or inpatient summary using CCD TemplateSurescripts Clinical Direct Messaging
Transmit to third party

Rationale: The system gives the patient the ability to view, download and transmit their CCD-A document. Once the patient views and downloads, the system offers the ability to transmit the document either encrypted or unencrypted. We feel that reviewing the transmission methods used as well as the frequency of utilization will best represent utilization of these features. By producing analytics on these results, we feel it will also help us identify those providers with low thresholds to reach out to them and provide them logic as to how to increase utilization.

Test Approach 1: De-identifiable data from system logs, will be extracted to produce analytic reports that will be reviewed to determine thresholds and methods of transmission used by the patients for transmitting CCD-A documents.

Expected Outcome(s): It is anticipated that patients will be able to share their electronic health information using the various transmission methods provided with no limitations and in compliance with the certification criteria, including the technical standards and vocabulary code sets.

Test Approach 2: Information of actions of download and transmit will be extracted from system logs to determine the success rate of patients downloading and transmitting documents. Transmission errors will be tracked and trended over time.

Expected Outcome: It is expected that patients will be able to share their information using the transmission methods provided with no limitations. The success/failure of the events will be logged and reviewed over time.

Care Setting(s)

ChartLogic Patient Portal is only marketed to the ambulatory practices using ChartLogic, therefore, only ambulatory practices will be used for Real World Testing.

SCHEDULE OF KEY MILESTONES

Key MilestoneDate/Timeframe
Begin collection of data laid out by planMarch 2024
Data Collection and ReviewQuarterly
End of Real World Testing for all measures.December, 2024
Final data review and analytics, create results reportJanuary 2025
Submit Real World Testing Results Report to ACBJanuary 2025

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 NameNicki Anderson, Director, Compliance
Authorized Representative Email: Nicki.Anderson@Medsphere.com
Authorized Representative Phone:      760-979-6531
Authorized Representative Signature:               Nicki Anderson
Date:  October 26, 2023