Firely Server
ONC Health IT Certified Solution
170.315(g)(10) – Standardized API for Patient and Population Services Certification Criteria
Certificate of Health IT Compliance
As of December 31, 2022, all EHR’s need to meet requirements for patient and population services criterion §170.315(g)(10) and get certified by ONC-Authorized Testing Labs.
Firely provides a turn-key FHIR Server, certified under the Office of the National Coordinator for Health Information Technology’s (ONC) Health IT Certification Program.
Certification details
HIT Vendor: Firely USA
Address: 228 East 45th Street, Suite 9E, New York, NY 10017
Phone number: (857) 263-3112
Date Certified: 05/02/2025
Product: Firely Server 6
Certification number: 15.04.04.3143.Fire.06.01.0.250502
Firely Server is certified for the below criteria of the ONC Health IT Certification Program
| 170.315(b)(10) | Electronic Health Information Export *Added: 06/29/2023 |
| 170.315(d)(1) | Authentication, Access Control, Authorization |
| 170.315(d)(9) | Trusted Connection |
| 170.315(d)(10) | Auditing Actions on Health Information |
| 170.315(d)(12) | Encrypt Authentication Credentials |
| 170.315(d)(13) | Multi-Factor Authentication |
| 170.315(g)(4) | Quality Management System |
| 170.315(g)(5) | Accessibility-Center Design |
| 170.315(g)(10) | Standardized API for Patient and Population Services |
This Health IT Module 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.
The certified endpoint of Firely Server is available for testing purposes only. The OpenAPI Swagger documentation is available here.
Price transparency
Firely Server pricing is a flat fee annual license for one (1) base instance to be used in a production environment and unlimited development and test instances. Certain packages include scaling instances. Firely does not charge based on data volumes, API calls, connected apps, patients, care providers or users, or infrastructure or hardware.
- A production instance is necessary for each unique database and in cases where conflicts between FHIR packages are detected by the Firely Server Administration API.
- Additional production instances may be needed for failover purposes, on-premise installations across multiple sites, or when end-users require complete data separation.
- Scaling instances must use the same environment and conformance resources as the production instance.
Included in the license fee for all packages is SMART on FHIR, standard support, FHIR updates and Firely Server upgrades (same package).
Firely Essentials – provides FHIR compliance and a limited set of features, tools, and plugins.
Firely Scale – provides advanced features and scaling capabilities designed to meet Government Authority Health Technology regulations. Firely Scale is ONC, ISiK and ISiP, MedMij and VIPP compliant out of the box. This package includes:
- All plugins
- All tools
- All features
- Launch Implementation Program
- Training Services
- Upgrades to meet mandated Health Technology regulations.
Firely CMS Compliance – includes all components of the Firely Scale package plus all mandated CMS-0057-F APIs and IG support.
- Upgrades to meet mandated CMS-0057-F regulations.
Not included in the license fee:
- The native Firely Server CQL engine for HEDIS, CMS, or custom CQL, which is licensed separately.
- Professional Services for custom and/or co-development, FHIR strategy development, and DevOps support.
Technical Documentation
All technical documentation required for evaluating, implementing and hosting Firely Server are available on the documentation site.
Trial Edition
The (g)(10) compliant Trial Edition of Firely Server can be downloaded here.
Please read the eBook How to Test Firely Server on Inferno to learn about testing your own instance of Firely Server against the ONC Inferno environment.
Scenarios
There are two ways in which you can use Firely Server to meet the (g)(10) certification criteria:
- Use certified software: you can use the Firely certification CHPL ID to add Firely as a module to meet the ONC Health IT Certification requirements. In this scenario, Firely Auth is required.
- Become certified yourself: you can use Firely Server to meet the technical requirements for the FHIR APIs in order to obtain certification. In this scenario, you can use your own Identity Provider for authentication and authorization in combination with the SMART on FHIR plugin (included in Firely Server).
Both scenarios require the Bulk Data Export plugin.
Firely Server FHIR Endpoints
Here you can find the endpoints of Firely Server installations using the Firely certification CHPL ID.
Conditions
The below conditions apply.
- No limitations or restrictions apply for using Firely Server, other than defined in the license for scaling.
- Firely will not maintain any relationship with end-users, e.g. customers or users of our customers, patients or third-party app developers, of the Firely Server API.
- In accessing data, there are no limitations or restrictions set by Firely.
- Firely does not have access to any PHI. Hosting and infrastructure are handled by the customer.
- Our customers are free to market, offer, and distribute products and services related to Firely Server within the scope of the license (the number of production instances).
- Firely guarantees the required support, maintenance, documentation to enable the implementation, deployment and use of Firely Server.
- The terms and conditions of Firely products apply. In addition to these terms and conditions, the all provisions on this page are part of the license agreement between Firely and customers who use Firely Server for the ONC Health IT Certification.
Standards Version Advancement Process (SVAP)
Updated: May 5, 2025
Under the ASTP/ONC’s Standards Version Advancement Process (SVAP), developers of certified health IT have the option to voluntarily certify their products to newer versions of adopted standards approved by the National Coordinator through the SVAP. Complying with SVAP adoption standards, Firely Server obtained certification on February 8, 2023, utilizing US Core 4.0.0 (USCDI v1), SMART App Launch 2.0.0, and Bulk Data 2.0.0. Firely commits to maintaining full support for previous US Core versions until they are deprecated by the National Coordinator.
US Core 7.0.0 (USCDI V4) & SMART App Launch 2.2.0 – November 15, 2024
In January 2025, Firely plans to voluntarily certify Firely Server 6 with US Core 7.0.0 (USCDI v4) and SMART App Launch 2.2.0. Firely Server 6 is already equipped with the necessary software to support clients interested in implementing US Core 7.0.0 and SMART App Launch 2.2.0, ensuring compatibility without disrupting existing implementations based on previous US Core or SMART App Launch versions.
US Core 6.1.0 (USCDI V3) – January 10, 2024
In February 2024, Firely plans to voluntarily certify Firely Server 5 with US Core 6.1.0 (USCDI v3). Firely Server 5 is already equipped with the necessary software to support clients interested in implementing US Core 6.1.0, ensuring compatibility without disrupting existing implementations based on previous US Core versions.
US Core 5.0.1 (USCDI V2) – June 29, 2023
In July 2023, Firely plans to voluntarily certify Firely Server 5 with US Core 5.0.1 (USCDI v2). Firely Server 5 is already equipped with the necessary software to support clients interested in implementing US Core 5.0.1, ensuring compatibility without disrupting existing implementations based on previous US Core versions.
Real World Testing Plans and Results
Under the ONC Health IT Certification Program, Certified Health IT developers are required to conduct Real World Testing (RWT) of their certified health IT (45 CFR 170.405). In accordance with Real World Testing requirements, Firely provides the following RWT plans and results: