This repository is used to:
- Collect issues spanning multiple repositories
- Collect issues from the community
Overview of the repositories currently maintained by the fdpg-plus project:
| Repository Name | Repository Information | Description |
|---|---|---|
| Blaze |    |
A FHIR® Server with internal, fast CQL Evaluation Engine |
| blazectl |   |
blazectl is a command line tool to control your FHIR® server |
| clinical-cohort-definition-language |  |
CCDL - formal definition of a cohort/feasibility |
| clinical-resource-transfer-definition-language | CRTDL - formal definition of a data extraction | |
| dataportal-availibility-updater | |
Update the availability information in Elastic Search according to a ontology |
| dataportal-es-init |  |
Initialises elastic search for the dataportal with ontology |
| feasibility-auth | Keycloak setup for dataportal (dev) | |
| feasibility-backend |      |
Backend of the feasibility-gui (dataportal) |
| feasibility-deploy | |
Shell scripts for feasibility deployment using docker compose |
| feasibility-gui |  |
Frontend UI for dataportal |
| feasibility-monitoring | |
Automatic monitoring for the Dataportal |
| fdpg-ontology-translation | |
Generates translations for ontologies using deepl |
| fdpg-plus | FDPG+ core repo | |
| fdpg-test-env |  |
Deployment of development environment for FDPG+ |
| fdpg-query-data-validation | |
Validate FDPG FHIR data quality |
| fhir-data-evaluator | |
Stratify FHIR data of a FHIR Server |
| fhir-ontology-generator | |
Generate FHIR ontologies |
| fhir-performance-test | Test the paging performance of your FHIR server | |
| fhir-server-examples | Docker & Makefile examples for FHIR servers | |
| flare | |
Execute a CCDL against FHIR server using FHIR search |
| kds-report | |
Creates kds-report and provides it |
| kds-report-converter | |
Convert DSF kds report to json formatted kds report |
| mii-process-feasibility | |
FDPG+ feasibility process plugins |
| mii-testdata | Assorted MII test-data tools and provisioning of testdata | |
| Projectathon7-VHF-DataExtraction | |
Data Extraction for Projectathon 7 |
| sq2cql |   |
Convert CCDL (before SQ) to CQL |
| torch |  |
Extracts data from FHIR Server according to CRTDL |
To create a coherent overview of all issues and how they relate to the release planning, we ask the community to mostly use this repository to submit new issues, unless the person adding an issue is certain which repository the issue belongs to. In this case, the person should create the issue directly in the appropriate repository.
1. Please ensure that any issue is described as clearly as possible.
2. When a new issue is submitted it will first have to be reviewed by one of us.
3. We will check the issue and give you feedback or ask additional questions.
4. On Issue acceptance: Creating sub issues or moving issue to the appropriate repository
- If your issue is accepted and spans multiple repositories, we will keep the issue in this repository, create the appropriate sub issues in the respective repositories, link them from the issue here and update the progress of this issue as it goes through our system.
- If your issue is accepted and only concerns one repository, we will create an issue in this repository, link this new issue from your created issue and close the issue here.
5. Issue low priority or out of scope
- Some issues might be considered within scope but very low priority due to resource constraints, which we would let you know via comment in your issue. In this case, you have the option to fork the repository(ies) and implement the feature yourself. We would ask you to let us know if you are planning to implement a feature yourself as we might consider merging it in the main repositories.
- Some issues might be considered out of scope. These issues are issues we would not merge into the main repositories. However, you have the option of maintaining a fork of the appropriate repository(ies) with your changes.