Support for MongoDB and Microsoft SQL Server provides the flexibility you need in schema design, scalability, and robust querying capabilities. FHIR’s structure, consisting of diverse and complex healthcare data types, aligns well with MongoDB’s document-based storage. SQL provides robust, structured querying capabilities, ensuring precise data retrieval and manipulation essential for healthcare data.

Hosting Firely Server anywhere provides the flexibility, scalability, and resilience needed to deliver an optimal system for your business. Organizations can choose between on-premises, cloud, or hybrid environments to best meet your security, compliance, and performance needs. This flexibility ensures that FHIR systems can scale with growing data volumes and support specific high availability and disaster recovery requirements.

Firely Server’s Premise-based deployment option ensures data security and compliance with stringent healthcare regulations. On-premises solutions provide organizations with full control over sensitive patient data, reducing the risk of breaches and unauthorized access. This deployment model also allows customization to meet specific institutional needs and integration with existing systems.

Firely Server supports CRUD REST APIs which provides a standardized way to create, read, update, and delete healthcare resources. Our solution also allows our users to easily intercept and customize the REST APIs.

Firely Server’s Basic FHIR validation ensures that your healthcare data conforms to FHIR standards, enhancing data accuracy, consistency, and interoperability. By validating data at the source, errors and inconsistencies are caught early, reducing the risk of downstream issues. Basic validation also simplifies compliance with healthcare regulations and standards.

Custom search parameters enable tailored querying of healthcare data, enhancing flexibility and efficiency in data retrieval. By allowing specific, user-defined criteria, they support the precise extraction of relevant information, which is crucial for clinical decision-making, research, and analytics.

Custom conformance resources enables organizations to tailor data standards to their specific use cases. They include extensions, profiles, and value sets that define how FHIR resources should be used in particular contexts. Organizations can use CCR to ensure compatibility with specific regulations, workflows, and data requirements while maintaining interoperability.

Firely Server implements different custom operations defined by the core FHIR specification or by the Implementation Guides required for different certifications. These operation include among others $document, $lastN, $docRef, $meta, $snapshot & $convert.
Note:
Firely Essentials does not include $lastN & $docRef
Firely dQM includes: $cql, Library/$evaluate & Measure/$evaluate-measure

Terminology services allows healthcare organizations to define and use specific FHIR vocabularies tailored to their needs. This includes creating custom code systems, value sets, and concept maps that standardize the meaning and usage of terms across different healthcare systems. Terminology services ensures that data is consistently understood and ultimately helps ensure interoperability between different FHIR systems. For more complex terminologies such as SNOMED CT and LOINC Firely Server can integrate with external FHIR-based terminology services.
Note:
Firely dQM includes; Custom FHIR-based terminology, Basic local terminology service & Integration with external terminology services

OpenTelemetry provides vendor-neutral observability information for collecting and analysing metrics and traces of Firely Server.

PubSub messaging enables real-time, event-driven communication by notifying subscribed systems of resource changes, ensuring scalable, decoupled interoperability.

Real World Testing is a process for recording and analyzing statistical data about the REST API behaviour of Firely Server. It allows for retrospectively gathering insights into the response codes of FHIR CRUD requests, as well as custom operations. The functionality enables the collection of all statistics needed for the Firely Server Real World Testing Plans. This is only available to US-based customers.

Our Firely Launch Implementation Program gives you access to our team of launch specialists who will ensure you get off to the smoothest possible start to your FHIR implementation.

Extensive support for authentication and authorization based on the latest version of SMART on FHIR. Data encryption and event logging by default including X-provenance header, $erase / $purge, Audit Logging and Access Policies.

Firely Server’s Multitenancy enables the sharing of a single instance of the system among multiple users or organizations, ensuring efficient resource utilization and cost-effectiveness. With the need for stringent data access control, multitenancy ensures that FHIR implementations can effectively accommodate diverse user groups and organizational requirements.

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.

Sharding only available for MongoDB.

CDS Hooks stands for Clinical Decision Support Hooks. CDS hooks are triggered by EHRs, invoking remote services that return CDS cards.

The standards and requirements established by the Centers for Medicare & Medicaid Services (CMS).

$member-match allows payors to uniquely and securely identify members based on demographic information.