Disclosure and Transparency
Disclosure:
Team Chart Concept (TCC) version 7.1 is compliant with the ONC Certification Criteria for Health IT and has been certified by an ONC-ACB in accordance with the applicable certification criteria adopted by the Secretary of Health and Human Services. This certification does not represent an endorsement by the U.S. Department of Health and Human Services.
Certified EHR Vendor and Product Information:
| Vendor/Developer Name: | Ulrich Medical Concepts |
| Certification Date: | 12.26.2019 |
| Certified EHR Name: | Team Chart Concept (TCC) |
| Certified EHR Versions: | 7.1 |
| CPHL Product #s: | 15.05.05.3049.UL15.01.00.1.191226 |
Clinical Quality Measures:
CMS 2v9, CMS 50v8, CMS 68v9, CMS 69v8, CMS 138v8, CMS 156v8, CMS 165v8
Certification Criteria:
| §170.315(a)(1) Computerized provider order entry (CPOE) – medications | §170.315(d)(1) Authentication, access control, authorization | §170.315(d)(13) Multi-factor Authentication |
| §170.315(a)(2) Computerized provider order entry (CPOE) – laboratory | §170.315(d)(2) Auditable events and tamper-resistance | §170.315(g)(2) Automated measure calculation |
| §170.315(a)(3) Computerized provider order entry (CPOE) – diagnostic imaging | §170.315(d)(3) Audit report(s) | §170.315(g)(3) Safety-enhanced design |
| §170.315(a)(4) Drug-drug, drug-allergy interaction checks for CPOE (NewCrop) | §170.315(d)(4) Amendments | §170.315(g)(4) Quality management system |
| §170.315(a)(5) Demographics | §170.315(d)(5) Automatic access time-out | §170.315(g)(5) Accessibility-centered design |
| §170.315(a)(9) Clinical Decision Support | §170.315(d)(6) Emergency access | §70.315(g)(6) Consolidated CDA Creation Performance |
| §170.315(a)(14) Implantable device list | §170.315(d)(7) End-user device encryption | §170.315(g)(7) Application access — patient selection |
| §170.315(b)(1) Transitions of Care | §170.315(d)(8) Integrity | §170.315(g)(9) Application access — all data request |
| §170.315(c)(1) Clinical Quality Measures – Record and Export | §170.315(d)(9) Trusted connection | §170.315(g)(10) Standardized API for patient and population services |
| §170.315(d)(12) Encrypt Authentication Credentials | §170.315(h)(1) Direct Project | §170.315(b)(10) Electronic Health Information (EHI) Export* |
*EHI can be exported in PDF or C-CDA format. Records for a patient are exported to one or more PDF/C-CDA files. The files created by the export are saved to a folder specified by the user.
Cost Transparency:
The Team Chart Concept (TCC) 7.1 application requires software license fees, implementation fees for installation/training, and annual maintenance fees post go-live. Additional costs include:
- NewCrop Core ePrescribing version 13.08
- Medfusion Patient Portal version 13.5
- EMR Direct Interoperability Engine
- Application Access API: UMC clients pay a one-time Application Access API setup fee and a monthly service fee.
- TCC Meaningful User Configuration: UMC Clients are not charged to upgrade to the latest certified version of TCC. Clients are billed a one-time setup fee to configure their system for Meaningful Use reporting.
- Patient Portal: UMC Clients pay a one-time Patient Portal setup fee and a monthly service fee.
- Direct Messaging: UMC clients pay a one-time Direct Messaging setup fee and monthly service fee per address.
Additional Software Required:
- EMR Direct Interoperability Engine
- NewCrop Core ePrescribing: UMC clients pay a one-time ePrescribing fee and a monthly service fee per prescriber.
Application Access API Additional Information:
API Documentation: Refer to the Interoperability Engine Open API Documentation for API implementation details including how to connect, API syntax, function names, required & optional parameters, and other information necessary to interact with the API.
API Terms of Use: Refer to the Interoperability Engine Open API Terms of Use for detailed terms and conditions for using the Interoperability Engine’s API. In addition to the Interoperability Engine Open API Terms of Use agreement, only authorized 3rd party vendors are allowed to access the API. Each UMC client will be responsible for providing authorization for access to their API by a 3rd party. Each UMC client may enforce their own Terms of Use regarding their instance of API Access.
API Base URL: Listed below are the base URL(s) for each UMC customer integrated with the FHIR API through the TCC EHR.
- There are currently no UMC customers integrated with the API.