3 reasons why Firely Server helps you meet (b)(10) requirements

Ready for EHI Exports

It supports the export EHI required by (b)(10). It enables authentication based on the SMART on FHIR specification.


Firely Server is a plug-and-play API for receiving and executing all (b)(10) export requests. This saves you time and effort.

Fully integrated

It’s deployable within your EHR ecosystem without creating dependencies or the need to change legacy systems.

The (b)(10) requirements
you need to fulfill

  • Support the export of a single patient EHI
  • Support the export of all EHI
  • Export files must be electronic and in a computable format that’s accessible via a public hyperlink
  • Limit the ability of users who can create export file(s)

Why choose Firely Server
for your (b)(10) compliance

  • All the features you need to be fully ONC compliant
  • 100% FHIR-based API
  • Plug into your proprietary systems. No need to change systems
  • Ready for EHI export with structured and unstructured data
  • Authentication based on the SMART on FHIR
  • Customizable in .NET or other tech stacks
  • Based on mapping done for (g)(10)
  • Created by one of the initiators of FHIR, it doesn’t get any better than this!
Logo ONC

Firely is certified under the Office of the National Coordinator for Health Information Technology’s (ONC) Health IT Certification Program. For more information go to the Mandatory Disclosures and API Documentation on our website.

§170.315 (b)(10) deadline is on the horizon. Read our blog.

Want to become (b)(10) compliant with
Firely Server?
Get more info about the options, prices and a smooth implementation

What happens next?

  1. We will contact you to schedule a 30-minute call
  2. You tell us about your company, challenges, needs and requirements
  3. We will ask additional questions to get a better understanding of what you need to see if there’s a fit with our product
  4. When you’re convinced, we will discuss prices and the implementation process