Certification Information
Production or Pre-Market Certification
Production Certification
Select this option if your EHR product is currently used in production environments. CCHIT will verify production use by contacting a reference site.
Pre-Market Conditional Certification
Select this option if you are seeking certification for an EHR product prepared for certification but is not yet installed in a production environment. If this product successfully passes CCHIT Certification, it will receive a conditional CCHIT Certification until its use in a production environment can be validated.
Commercial or Internal Use
EHR Product Developed for Commercial Use
For CCHIT, a commercial EHR product is one that was developed for the primary purpose of being installed and used in sites other than that of the developer. (Most products seeking CCHIT Certification fall into this category.)
EHR Product Developed for Internal Use
For CCHIT, an internally developed EHR product is one that was primarily developed for a specific organization’s internal use.
Single or Joint Applicants
Single Comprehensive Product Application
Choose this option for individual comprehensive EHR products that meet, or can assign, all CCHIT required criteria without the assistance of additional products.
Joint Certification (Single Applicant)
For EHR systems where multiple products from the same Applicant are needed to meet the certification criteria. The Applicant must list here: each product name, version, release/version number and release date.
Joint Certification (Multiple Applicants)
For EHR systems where multiple products are needed to meet the certification criteria and together, multiple Applicants seek joint certification, one Applicant must serve as prime on the application below. Other co-applicants must be also listed.
Product Configuration Information
The CCHIT inspection process requires the applicant to define the product seeking certification. The applicant must identity all of its components including hardware, software, operating system, communication method, configuration information, delivery model, etc., which are needed to satisfy CCHIT’s certification criteria. CCHIT’s Security Criteria and test scripts require the examination of this information to determine the product’s compliance with CCHIT’s criteria and test scripts.
Product Configuration Information is also used to accurately identify the certified EHR product to purchasers, and is listed in the CCHIT’s Certified Product Directory. Refer to the Certification Handbook for more details about this disclosure process, and how you can list Additional Configurations of your Certified Product. The Product Configuration Information you supply with this application (entered below) should exactly match the configuration to be tested in the inspection process.
The EHR product seeking certification is defined to include all of the components necessary to provide the functionality defined in the certification criteria (e.g. hardware, operating systems, database management systems (DBMS), drug information database, clinical practice guidelines, backup utilities, third-party software applications, etc.). Applicants must fully describe the product being presented to be certified and all of its components, including their version numbers where applicable.
Note: Only one platform or system configuration is testable for each certification. Please ensure that you provide just the single configuration or system platform that will be used on the day of your CCHIT test for the “To be Certified” section on this form.
Enter a description of the EHR product presented for CCHIT certification (300 words or less)
Client/Server
This configuration typically consists of a "thick" client communicating directly with a back-end database server. Application logic can be coded either in the client, or in database procedures, or both.
Thin Client
Extending a Client/Server configuration to run with Microsoft Terminal Services, or Citrix Presentation Servers so users can interact with the application through a "thin client" (terminal or software).
Web Application
Web applications have 3 or sometimes 4 tiers, and usually consist of a web (and possibly an application) server transacting with a database server, while presenting the user interface through web browsers.
Vendor Hosted
EHR vendor owns and operates the database, application and/or web servers for use by customers.
3rd Party Hosted
Another 3rd party company is contracted by EHR vendor to operate and manage the database/application/web servers used by customers.
Customer Hosted
Customer is expected to own and operate their own servers -- or can directly contract with another party for hosting.
Other Components:
List here any drug information databases, clinical practice guidelines, backup utilities, third-party software applications, etc. packaged with your EHR product.
Indicate "None" if there are no other components.
Review and re-select your configuration responses to match what you intend to bring to the Certification inspection process.
All other product configurations can be entered later as "Additional Configurations" to your product entry in the CCHIT EHR Product Directory. See the CCHIT Certification Handbook for more details on this.