You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,7 @@ A demo installation can be found [here](https://blaze.life.uni-leipzig.de/fhir)
20
20
21
21
Blaze is widely used in the [Medical Informatics Initiative](https://www.medizininformatik-initiative.de) in Germany and in [Biobanks](https://www.bbmri-eric.eu) across Europe. A 1.0 version is expected in the next months.
22
22
23
-
Latest release: [v0.30.0][5]
23
+
Latest release: [v0.30.1][5]
24
24
25
25
## Quick Start
26
26
@@ -76,7 +76,7 @@ Unless required by applicable law or agreed to in writing, software distributed
Copy file name to clipboardExpand all lines: docs/api.md
+3Lines changed: 3 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -52,6 +52,9 @@ By default Blaze enforces referential integrity while deleting resources. So res
52
52
53
53
### Delete History
54
54
55
+
> [!CAUTION]
56
+
> The delete history interaction is currently **alpha** and has to be enabled explicitly by setting the env var `ENABLE_INTERACTION_DELETE_HISTORY` to true. Please don't use it in production. Please be aware that the database might not be able to migrate to a newer version of Blaze if the operation was used.
57
+
55
58
> [!CAUTION]
56
59
> The delete history interaction is trial use in the unreleased next version of FHIR. So it is subject to change. Please use it with care.
Copy file name to clipboardExpand all lines: docs/api/operation-patient-purge.md
+5-2Lines changed: 5 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,10 @@
1
-
# Operation Patient Purge
1
+
# Operation \$purge on Patient
2
2
3
3
> [!CAUTION]
4
-
> The patient $purge operation is trial use in the unreleased next version of FHIR. So it is subject to change. Please use it with care.
4
+
> The operation \$purge on patient is currently **alpha** and has to be enabled explicitly by setting the env var `ENABLE_OPERATION_PATIENT_PURGE` to true. Please don't use it in production. Please be aware that the database might not be able to migrate to a newer version of Blaze if the operation was used.
5
+
6
+
> [!CAUTION]
7
+
> The operation \$purge on patient is trial use in the unreleased next version of FHIR (R6). So it is subject to change. Please use it with care.
5
8
6
9
The patient \$purge operation is used to request the removal of all current and historical versions for all resources in a patient compartment. The return is an OperationOutcome with results and/or details about execution. The `code` of the first issue of the OperationOutcome is either `success` on successful purging of all resources or an error.
0 commit comments