Test Firely Server
How-to's
7 Min Read

Evaluating Firely Server is quick and easy. Here are the two best ways to check it out.

Photo of Alexander Zautke
Alexander Zautke

Subscribe to our newsletter

Subscribe

Firely Server answers the need for a stable server that can be used 24/7 in a range of demanding environments. Created by one of the initiators of FHIR, it’s a turn-key FHIR Server that’s reliable and easy to use: built in .NET CORE, it’s compliant with regulation, and offers unparalleled support for the FHIR standard.

You’ll obviously want to check it out before you make a purchase. There are two main ways to do just that, but it’s not always obvious which one to choose. That’s something we wanted to clarify, so this article explains how to evaluate Firely Server – with or without a download.

Desicion tree

Choosing your route 

The route you choose will depend on your role, where you are in your decision-making, the level of detail you need, and the questions you need to answer. It’s also important to pick the method you’re most comfortable with. The two main options are:

  1. Downloading the trial version of Firely Server
  2. Exploring our public endpoint using Postman (or our Swagger UI)

If you’ve just begun searching the market for solutions, testing a few high-level functionalities using our public endpoint may be exactly what you need. But if you’re further down the road toward implementation, the trial version offers a valuable way to experience the full functionality of Firely Server, test it against your own data, and see how it interacts with all your applications.

  

OPTION 1

Firely Server – Trial License

By far the most popular option with developers is downloading a feature-complete version of Firely Server for a full week of unrestricted testing. This gives you a comprehensive view of the product so you can explore how it meets your technical requirements. 

Trail license icon

With this assessment method, you can run Firely Server with your own data and your own conformance resources, such as FHIR profiles, and search parameters, and test how it deploys in your own infrastructure. The only limitation is that it needs to be manually restarted every 24 hours. 

Public endpoint icon
OPTION 2

The public endpoint

If you’re just starting to research your options, our public endpoint is a quick and simple way to verify that Firely Server works and is compatible (for example) with (g)(10), CMS, or ISiK / ISiP.

If you’re already familiar with the FHIR standard, accessing the public endpoint with a Postman account gives you the freedom to create your own requests and try out specifics without being restricted by pre-defined templates or involving your own server.

We’ve also developed a Swagger UI so you can try out some basic interactions – but you won’t be able to execute custom operations.

Making the choice

If you just want to put your toe in the water, to find out what our product does and how well it works, then using the public endpoint is probably the fastest and most convenient choice. The same thing applies if you’re a technical manager looking for a straightforward way to get a handle on the product, or an executive tasking your developers with an initial assessment of suitable products.

But if you’re closer to making a decision, or you want to jump right in to the detail, you’ll probably opt to download Firely Server.

A third option for educational, third sector, and training purposes is our Community Edition. It’s free to use but comes with some limitations, and it’s not suitable for running in ‘production mode’ such as a hospital setting.

Talk to us  

If you’ve experienced unexpected challenges with EHR interoperability, need help in meeting (g)(10) certification, or simply want to harness the full power of FHIR, feel free to get in touch.  

Want to stay on top of Interoperability and Health IT? 

Subscribe to our newsletter for the latest news on FHIR. 

Post a comment

Your email address will not be published. Required fields are marked *