General Information
|
Developer Name |
NaphCare |
|
Product Name(s) |
TechCare EHR |
|
Version Number(s) |
5.0 |
|
Certified Health IT |
2015 Edition |
|
Product List (CHPL) ID(s) |
15.04.04.2813.Tech.05.00.0.191208 |
|
Developer RWT Page URL |
https://devportal.techcareehr.com/RWTP |
Standards Updates
|
Standard (and version) |
USCDI v3 |
|
Updated certification criteria & associated
product |
B1, G9 |
|
Health IT Module CHPL ID |
15.04.04.2813.Tech.05.00.0.191208 |
|
Real World Testing Plan & Results Page URL: |
Changes to Original Plan
|
Summary of Change |
Reason |
Impact |
|
Use Case 1: Care Coordination and Electronic Exchange No Testing
performed |
No Testing performed
per the enforcement discretion here: |
N/A |
|
Use Case 2: Electronic Health Information Export No
Testing performed |
No Testing performed
per the enforcement discretion here: |
N/A |
|
Use Case 3: Clinical Quality Measures (CQM) No Testing performed |
No Testing performed
per the enforcement discretion here: |
N/A |
|
Use Case 4: The corrections-specific industry that is our care setting did not see direct correlation with this use case and we were unable to identify participating partners to complete this study. |
Although functionality exists for Record and
Export, Application Access and is available in production environments, we
were not able to find willing participants. |
This prevented NaphCare from being able to
document and measure the success of this measure in a real-world use
case. To meet testing requirements,
testing was
performed in the staging environment which mirrors
production. |
Summary of Testing Methods and Key Findings
It was NaphCare’s intent to use TechCare’s
Reporting/Logging features to examine functionality performed in the system and
the success/failure with the tested measures within each use case
defined. This would, in turn:
· Demonstrate
real world interoperability and conformance to criterion requirements
· Include
patient care scenario and use case focused testing
Specifically, NaphCare planned to use the
following data sources to collect and confirm testing approaches:
· TechCare
Application Logging reflecting end user actions in the system
· TechCare
Interface Logging reflecting automated action within the system
· Interface
Partner Results (i.e., partner Hospitals to validate information
requested/received)
· End-User
Sample Sets (i.e., subset of patients meeting criteria for information transfer)
Use
Case #1: Care Coordination and Direct Project
o
§ 170.315(b)(1) Transitions of care
o
§ 170.315(h)(1) Direct Project
o
§ 170.315(b)(6) Data Export
o
§ 170.315(c)(1) Record and Export
Use
Case #4: Application Programming Interfaces (APIs)
o
§ 170.315(g)(7) Application Access— Patient Selection
o
§ 170.315(g)(9) Application Access— All Data Request
o
§ 170.315(g)(10) Standardized Request for patient and population
services
Care Setting
The TechCare EHR
product is deployed to correctional healthcare settings within county, state,
and federal correctional facilities. These are the only care settings where
TechCare EHR is utilized, and partners in this industry would represent testing
subjects.
Metrics and Outcomes
Use Case 1: Care Coordination and Direct Project:
· Criterion
§170.315(b)(1) Transitions of Care
· Criterion
§170.315(h)(1) Direct Project
|
Measurement/ Metric |
This use case is associated with two
different criteria and tracking two different metrics. It will be used to track and count how many
C-CDAs are created successfully, and then sent and received via Direct
Project connecting to a HISP for successful transmission. |
|
Expected Outcome(s) |
·
95% of patients
seen for a Telehealth encounter by a specialty care provider had a C-CDA
created. ·
66% of C-CDAs
created are sent electronically to the Telehealth Care provider
electronically. ·
66% of patients
receive a C-CDAs from Telehealth Care provider electronically upon completion
of the scheduled Telehealth event. |
|
Outcomes |
No
testing performed |
|
Challenges Encountered
(if Applicable) |
N/A |
Use Case 2: Data Export
· Criterion
§170.315(b)(6) Data Export
|
Measurement/ Metric |
This use case is tracking a complete batch
export comparing the number of actual patients with a health information
record (within the EHR system) to the number of electronically exported
C-CDAs created using the EHR export functionality. The planned testing scenario was exporting
patient C-CDAs from TechCare to another EHR vendor. |
|
Expected Outcome(s) |
100% of eligible C-CDAs are exported in bulk. |
|
Outcomes |
No testing performed |
|
Challenges Encountered
(if Applicable) |
N/A |
Use Case 3: CQM
· Criterion
§170.315(c)(1) Record and Export
|
Measurement/ Metric |
This
use case tracks the number of CQM data that is exported and compares it to
the number of data elements the users enter.
This test focus is primarily to determine whether the user is
correctly entering the required data.
Test results not meeting the expected outcome indicate that user
training is required. |
|
Expected Outcome(s) |
35%
of exported CQM exported will contain the required data elements. |
|
Outcomes |
No testing performed |
|
Challenges Encountered
(if Applicable) |
N/A |
Use Case 4: Application Programming Interfaces (API)
· Criterion
§170.315(g)(7) Application Access – Patient Selection
· Criterion
§170.315(g)(9) Application Access – All Data Request
· Criterion
§170.315(g)(10) Standardized API for patient and population services
|
Measurement/ Metric |
This
use case captures the total number of validated API request that resulted in
received (intake) or generated (discharge) C-CDA records, compared with total
opportunities to ingest or send useful information from a neighboring system. |
|
Expected Outcome(s) |
25%
of the patients received into a new facility will have health history
transferable via electronic C-CDA. 25% of the released from a
facility will be rebooked into another facility and have records requested of
them. 75% of the patients will
either not have been booked before, or will not be released and rebooked
within the reporting period in a neighboring facility. |
|
Outcomes |
None of our participating facilities had
neighboring facilities with the functionality for sending or receiving
C-CDAs. Testing was performed in our staging
environment which mirrors production. · Numerator: 2,421
test patients were used to request C-CDAs via API ·
Denominator: 2,421
of the C-CDAs were successfully received · Results:
100% · Numerator:
1,898 test patients requested records via API ·
Denominator:
1,898 of the C-CDAs were successfully sent ·
Results: 100% |
|
Challenges Encountered
(if Applicable) |
Due to lack of request for patient data we
were unable to test transferring C-CDAs in the production environment. Due to lack of technology from facilities
patients booked into our facilities we were unable to test receiving C-CDA’s
via API in our production environment. |
Key Milestones
|
Milestone |
Care Setting |
Date |
|
Finalization of all Application
Functionality/Modules including data collection mechanisms for Use Case 4. |
Correctional Healthcare (Jails, Prisons) |
December 2025 (TechCare v5.0 2025/R6) |
Attestation
The Real
World Testing Results above are 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 Read-World Testing requirements.
|
Authorized Representative Name:
|
Jason Douglas, Chief Technology Officer |
|
Authorized Representative Email:
|
jdouglas@naphcare.com |
|
Authorized Representative Phone:
|
205-536-8445 |
|
Authorized Representative Signature:
|
|
|
Date: |
01/30/2026 |
