Re: FHIR server implementation having a RDF triplestore

Hi Daniel,

of course, there are plenty of, so even about a decade ago we were able to
benchmark some half a dozen of those, none perfect, you just need to decide
on what is of most import for you.
As far as we are concerned, the decision was to stay with the Open Link
Virtuoso implementation at that time, one of the advantages being that you
were free to flip from an RDF endpoint to a  conventional SQL database at
no cost.
We may still revise our decision, of course, given the options available
nowadays, yet what I can at least say is that Virtuoso does work.

Cheers.

On Thu, 27 Jan 2022 at 15:59, Daniel Teixeira <ddtxra@gmail.com> wrote:

> Dear community,
> I am looking for a FHIR implementation (server) that stores the resources
> in native RDF FHIR, so that I could do complex SPARQL queries on top of the
> database, but also expose REST API endpoints in FHIR. (Not so much
> interested in the U from CRUD, but at least Create, Read and Delete would
> be enough)
>
> For example what I would like to query on the FHIR store would be
> something like:
> * Retrieve all patients that are older than 18, not dead, having a body
> weight bigger than 100kg and that have laboratory of insulin higher than
> xyz .
>
> Unfortunately I can only find FHIR server implementations with a RDBMS or
> mongo as data storage . Do you know if some FHIR server implementations
> exists with an RDF triplestore as data storage where the TTL of FHIR
> resources would be stored natively?
>
> Thanks for your help.
>
>