Firely Launch – from purchase to production

Firely Launch Deliverables

While every FHIR implementation is different we deliver a consistent outcome with our Firely Launch program. These deliverables usually include the following:

Primary Use Case Definition

After going through the Firely Launch Program, Firely Server will be configured to meet the requirements of your primary use case. A clear definition of the use case including goals, timelines, and stakeholders is pivotal for a successful project execution.

Architectural Design

Using your primary use case, we will collaborate on the architectural design. This design includes choices about hosting environments and backend databases, data mapping, authentication, ETL (Data Loading or Facade), any 3rd party integrations required, and custom plugins.

Define Access

Your Firely Server will be fully configured to include the right setup to grant access to a diverse set of clients that can enable systems, providers, patients, and others to access your data securely.

Customized Guidance

No FHIR implementation is the same. Firely Launch gives you access to additional project-specific advice to help your team navigate complex decisions and confidently manage your FHIR implementation so you can spend less time configuring the server and more time focusing on your application requirements and workflows.

Firely Launch Program

The Firely Launch program includes several workshops designed to streamline your implementation and fast-track success. These sessions allow your team and our consultants to collaborate on system design, implement solutions, and address any concerns for a more efficient deployment. Each session provides your team the opportunity to implement the discussed options, then address any concerns, roadblocks, or questions related to the configuration and setup.

The sessions include:

Technical Review

Detailed review and questionnaire for your primary use case and implementation requirements. 

Installation in Your Environment

Review Firely Server installation requirements for on-premise, cloud web app, Kubernetes, or other environments.

Connecting to Your Data Sources

Explore the right options for initial loading and syncing your data via the API, Firely Server Ingest, Firely PubSub, or Facade.

Granting Access to Clients

Evaluate options for granting access to Firely Server for secure internal and external client access.

Server Architectures

Assess choices for setting up scaling instances and Firely Server’s role in different architectures.

Implementation Strategy Final Review

Plan production timelines and resource needs for a successful deployment.