This repository was archived by the owner on Jan 4, 2023. It is now read-only.
Exemples de requêtes Fhirbase #9
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…nd danger thresholds for certain modules
adriencanterot
requested review from
CorneliuMalciu,
KouakouVerde and
alexisthual
KouakouVerde
approved these changes
Jun 5, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Cette PR contient des exemples de requêtes Fhirbase dans un notebook jupyter adaptées aux données affichées du Dashboard.
Il s'agit de requêtes SQL utilisant les sélecteurs de Fhirbase pour naviguer dans l'architecture des objets FHIR.
Les exemples de requêtes comprennent :
Certaines requêtes ne renvoient pas de résultats avec la mock database de Fhirbase couplée à celle de MIMIC à cause de données manquantes.
En naviguant dans l'architecture des objects FHIR, on note que le standard est très malléable et permet, pour 1 use case donné, plusieurs façons de le modéliser. Les requêtes ne sont pas forcément simples / exhaustives, surtout en travaillant avec des bases de données extérieures.
J'ai mis cette PR dans le Dashboard car les requêtes sont directement liées à ce qui est affiché au niveau de front. Ça reste une base de travail si jamais un serveur devait être développé.