Lets choose the best option for you.
Free | Enterprise | |
---|---|---|
FHIR compliant repository for health related data (See RESTful API and Search documentations) | ||
CRUD Operations | ✔ | ✔ |
Resource based search (e.g. /Condition?param=...) | ✔ | ✔ |
Compartment based search (e.g. /Patient/pid/Condition?param=...) | ✔ | ✔ |
General search | ✔ | ✔ |
Batch operation | ✖ | ✔ |
Transaction operation | ✖ | ✔ |
vread and history operations | ✖ | ✔ |
FHIR Documents | ✖ | ✔ |
Advance FHIR functionalities (include/contained resources, advance search, text search, FHIR operations, etc) | ✖ | ✔ |
Easily configurable with FHIR Infrastructure resources (Conformance, StructureDefinition, etc); self-definition of system functionality | ||
Configurable to support any base FHIR version (DSTU2, STU3) | ✔ | ✔ |
Configurable in terms of which resources you want to support and which profiles for each resource | ✔ | ✔ |
Configurable in terms of which REST operations are supported for each resource | ✔ | ✔ |
Configurable in terms of which search parameters you want to support for each resource | ✔ | ✔ |
Configurable in terms of which search mechanisms you want to support | ✔ | ✔ |
Configurable in terms of which FHIR compartments you want to support for compartment based search | ✔ | ✔ |
Validation of resources before update and create | ||
Base FHIR validation | ✔ | ✔ |
Validation against profile | ✔ | ✔ |
Performance/Scalability | ||
Tuned/deployed on single MongoDB instance (restrictions on number of records) | ✔ | ✔ |
Tuning write and search performance for each type of resource (DB index creation based on configurations) | ✖ | ✔ |
Enabling separate collection for profiles to improve performance? | ✖ | ✔ |
Horizontal Scalability (sharding; configured based on each resource) | ✖ | ✔ |
Replication | ✖ | ✔ |
Privacy/Security | ||
Configurable for https (given a X509 certificate) | ✔ | ✔ |
CORS | ✔ | ✔ |
Configurable for certificate based client authentication (confidential clients) | ✖ | ✔ |
Authorization based on Oauth bearer token (extension of JSON web token spec for FHIR based access) including the permissions given to the client (comply with UMA resource server) | ✖ | ✔ |
Auditing System (create audits and self store or send them to FHIR based Audit Server?) | ✖ | ✔ |
Encryption at rest ? | ✖ | ✔ |
Support pseudonymization for Patient (+Patient Identity Management by an trusted authority)? | ✖ | ✔ |
System Monitoring (Administrative web based dashboard) | ||
Number of records, storage, query performance, etc | ✖ | ✔ |
User Management and Authentication for Small Scale Health Applications | ||
User registration (Patient, Physician, Related Person, ...) and identity management | ✖ | ✔ |
Single-sign-on page with 2-factor and 3-factor authentication | ✖ | ✔ |
OpenID Connect Authentication Service | ✖ | ✔ |
OpenID Connect UserInfo Service | ✖ | ✔ |
Patient Identity Management (Mappings of FHIR psedudoynm to real identity) | ✖ | ✖ |
Authorization and Privacy Management | ||
Configurable for roles and resource types | ✖ | ✔ |
Enterprise access control policy definition and management for FHIR (default policy for resources, required permissions to continue care) | ✖ | ✔ |
Patient consent definition and management for FHIR repo | ✖ | ✔ |
UMA Authorization Service (for FHIR) | ✖ | ✔ |
Audit View | ✖ | ✔ |
Audit Repository | ✖ | ✔ |
Patient managed external account integrations (Fitbit, open mHealth) | ✖ | ✔ |
Data Integrators | ||
onFHIR.io KAFKA client for Java | ✖ | ✔ |
IHE XDR service based integration | ✖ | ✔ |
CCD/CDA Integration | ✖ | ✔ |
HealthKit integration | ✖ | ✔ |