Skip to content

Commit

Permalink
Release v1.1.0
Browse files Browse the repository at this point in the history
  • Loading branch information
bastianschaffer committed Oct 30, 2024
1 parent 131539c commit 18427b3
Show file tree
Hide file tree
Showing 5 changed files with 14 additions and 6 deletions.
6 changes: 6 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,12 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
### Fixed
### Security

## [1.1.0] - 2024-10-30

### Added
- Add Support for OAuth Authentication
- Add Sending Measure Report to FHIR Server

## [1.0.0] - 2024-09-25

### Added
Expand Down
2 changes: 2 additions & 0 deletions DEVELOPMENT.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,12 +6,14 @@
* rename every occurrence of the old version, say `2.2.0-SNAPSHOT` into the new version, say `2.2.0`
* rename every occurrence of old Docker images like `ghcr.io/medizininformatik-initiative/fhir-data-evaluator:0.1.0`
into the new image, say `ghcr.io/medizininformatik-initiative/fhir-data-evaluator:0.1.1`
* rename the Docker image in the [docker-compose](docker/docker-compose.yml) from develop into the new version
* update the CHANGELOG based on the milestone
* create a commit with the title `Release v<version>`
* create a PR from the release branch into main
* merge that PR
* create and push a tag called `v<version>` like `v0.1.1` on main at the merge commit
* create a new branch called `next-dev` on top of the release branch
* change the version in the POM to the next SNAPSHOT version which usually increments the minor version
* change the Docker image in the [docker-compose](docker/docker-compose.yml) to develop
* merge the `next-dev` branch back into develop
* create release notes on GitHub
8 changes: 4 additions & 4 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -39,12 +39,12 @@ An example of a Measure can be found [here](Documentation/example-measures/examp

### MeasureReport as Output only:
```sh
docker run -v <your/measurefile.json>:/app/measure.json -v <your/output/dir>:/app/output -e FHIR_SERVER=<http://your-fhir-server/fhir> -e TZ=Europe/Berlin -it ghcr.io/medizininformatik-initiative/fhir-data-evaluator:1.0.0
docker run -v <your/measurefile.json>:/app/measure.json -v <your/output/dir>:/app/output -e FHIR_SERVER=<http://your-fhir-server/fhir> -e TZ=Europe/Berlin -it ghcr.io/medizininformatik-initiative/fhir-data-evaluator:1.1.0
```
### MeasureReport and CSV Output:

```sh
docker run -v <your/measurefile.json>:/app/measure.json -v <your/output/dir>:/app/output -e CONVERT_TO_CSV=true -e FHIR_SERVER=<http://your-fhir-server/fhir> -e TZ=Europe/Berlin -it ghcr.io/medizininformatik-initiative/fhir-data-evaluator:1.0.0
docker run -v <your/measurefile.json>:/app/measure.json -v <your/output/dir>:/app/output -e CONVERT_TO_CSV=true -e FHIR_SERVER=<http://your-fhir-server/fhir> -e TZ=Europe/Berlin -it ghcr.io/medizininformatik-initiative/fhir-data-evaluator:1.1.0
```
* this generates a CSV file for each Stratifier and stores the files in a directory named after the current date combined
with the Measure's name
Expand All @@ -53,7 +53,7 @@ with the Measure's name
### Usage with Docker Networks
* to any of the listed docker run commands add ```--network <your_network>``` to run the container inside a Docker network
```sh
docker run -v <your/measurefile.json>:/app/measure.json -v <your/output/dir>:/app/output -e CONVERT_TO_CSV=true -e FHIR_SERVER=<http://your-fhir-server/fhir> -e TZ=Europe/Berlin --network <your_network> -it ghcr.io/medizininformatik-initiative/fhir-data-evaluator:1.0.0
docker run -v <your/measurefile.json>:/app/measure.json -v <your/output/dir>:/app/output -e CONVERT_TO_CSV=true -e FHIR_SERVER=<http://your-fhir-server/fhir> -e TZ=Europe/Berlin --network <your_network> -it ghcr.io/medizininformatik-initiative/fhir-data-evaluator:1.1.0
```

### Time Zones
Expand All @@ -68,7 +68,7 @@ The environment variables are used inside the docker container, so if they are s
be visible in the container. Each additional environment variable can be passed using the `-e` flag.
* Example of passing a page count of 50:
```sh
docker run -v <your/measurefile.json>:/app/measure.json -v <your/output/dir>:/app/output -e FHIR_SERVER=<http://your-fhir-server/fhir> -e FHIR_PAGE_COUNT=50 -e TZ=Europe/Berlin -it ghcr.io/medizininformatik-initiative/fhir-data-evaluator:1.0.0
docker run -v <your/measurefile.json>:/app/measure.json -v <your/output/dir>:/app/output -e FHIR_SERVER=<http://your-fhir-server/fhir> -e FHIR_PAGE_COUNT=50 -e TZ=Europe/Berlin -it ghcr.io/medizininformatik-initiative/fhir-data-evaluator:1.1.0
```

### Sending the MeasureReport to a FHIR Server
Expand Down
2 changes: 1 addition & 1 deletion docker/docker-compose.yml
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
services:
fhir-data-evaluator:
image: ghcr.io/medizininformatik-initiative/fhir-data-evaluator:develop
image: ghcr.io/medizininformatik-initiative/fhir-data-evaluator:1.1.0
environment:
CONVERT_TO_CSV: ${FDE_CONVERT_TO_CSV:-true}
FHIR_SERVER: ${FDE_FHIR_SERVER:-http://localhost:8080/fhir}
Expand Down
2 changes: 1 addition & 1 deletion pom.xml
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@
</parent>
<groupId>de.medizininformatikinitiative</groupId>
<artifactId>fhir_data_evaluator</artifactId>
<version>1.1.0-SNAPSHOT</version>
<version>1.1.0</version>
<name>Fhir Data Evaluator</name>
<description>Fhir Data Evaluator</description>
<properties>
Expand Down

0 comments on commit 18427b3

Please sign in to comment.