DavidStables (talk | contribs) (Created page with "Having an information model is one thing. Querying it to extract data is another.") |
DavidStables (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
Having an information model is one thing. Querying it to extract data is another. | Having an information model is one thing. Querying it to extract data is another. | ||
As an RDF Graph knowledge base the information model can be directly queried using SPARQL. | |||
However, as Health records are likely to be stored as relational, or at least SQL compatible, data bases, querying health records that are aligned with the model will require SQL. | |||
The gap between plain language query and SQL or SPARQL is large and direct mappings between one and the other have not proved successful. It is unlikely that most users will be able to build complex queries directly in either SQL or SPARQL. | |||
Query applications use various domain specific languages to bridge from user friendly screens to the lower level languages that actually retrieve or update data. | |||
Information model has three main categories of use case that require such a bridge: | |||
a) Query of the information model content by end users e.g. finding concepts | |||
b) Query by the information model applications via the IM APIs to retrieve objects for display or update the stored objects | |||
c) Query by health staff of implemented health records. | |||
Revision as of 14:29, 29 March 2022
Having an information model is one thing. Querying it to extract data is another.
As an RDF Graph knowledge base the information model can be directly queried using SPARQL.
However, as Health records are likely to be stored as relational, or at least SQL compatible, data bases, querying health records that are aligned with the model will require SQL.
The gap between plain language query and SQL or SPARQL is large and direct mappings between one and the other have not proved successful. It is unlikely that most users will be able to build complex queries directly in either SQL or SPARQL.
Query applications use various domain specific languages to bridge from user friendly screens to the lower level languages that actually retrieve or update data.
Information model has three main categories of use case that require such a bridge: a) Query of the information model content by end users e.g. finding concepts b) Query by the information model applications via the IM APIs to retrieve objects for display or update the stored objects c) Query by health staff of implemented health records.