Vonk FHIR Server is an integrated, turn-key FHIR server with storage capabilities (a FHIR repository). Vonk supports all resource types and search parameters in the FHIR specification, including profiled resources. Vonk’s FHIR RESTful API allows access to the resources in the repository.
There are some typical scenarios where you would choose Vonk FHIR Server over a Vonk Facade such as:
- You want to FHIR-enable your data, but don’t want to put that load on your production systems.
- You want to FHIR-enable your data and get support for complex search operations out of the box.
- You need CRUD support for FHIR resources, but backend systems do not support this.
- You need storage for a new application that uses FHIR resources from the start.
- Other parties want to send FHIR data to you, and Vonk acts as a staging area for incoming data – to be processed by back end systems later.
If you want to load data from existing (non-FHIR) systems, you can map this data to the FHIR data model before loading them into Vonk FHIR Server. Since this happens outside of Vonk any system and technology that can deliver FHIR resources in JSON or XML to the RESTful endpoint will do. But if you need better and faster support for data mapping, consider putting Vonk FHIR Facade in front of the legacy system(s).
Storage of FHIR resources needs to be safe, reliable and must fit in your infrastructure. Vonk FHIR Server has native support for SQL Server, SQLite and MongoDB. These are databases from totally different paradigms (relational vs document), showing the flexibility of the Vonk storage engine. So other database engines, e.g. Oracle, PostgreSQL, MySQL or Microsoft DocumentDB, can easily be accommodated. We intend to expand database support based on customer requests.
Lastly, Vonk FHIR Server also supports in-memory storage. This is ideal for integration testing in app development.
Vonk FHIR Server can be extended with OAuth2 and OpenIdConnect authentication. This also means that Vonk can participate in a Single Sign-on environment. Access to resources can be based on SMART-on-FHIR scopes and launch context. Examples of this are:
- Vonk FHIR Server powers a Patient portal, and the patient gets just read-only access to resources that are related to him/herself.
- Vonk FHIR Server powers a specialized mobile app geared towards the physician. He/she then gets access only to the resources that are related to the current Encounter.
Of course Vonk FHIR Server comes with support for https and can be fronted by reverse proxies or load balancing web servers. Data at rest is not encrypted by Vonk itself, but can be encrypted by the database engine, e.g. by Transparent Data Encryption on SQL Server or the Encrypted Storage Engine on MongoDB.
Vonk fits in with different infrastructure preferences. Available options are:
- Dockerized, also within Kubernetes
- Stand-alone, cross-platform binaries
- Azure App Service
- IIS Web application