added more content to upcoming changes

CARA-ch · Dec 12, 2023 · 1ff4bc4 · 1ff4bc4
1 parent 0d8a739
commit 1ff4bc4
Showing 1 changed file with 43 additions and 1 deletion.
diff --git a/docs/other/upcoming_changes.md b/docs/other/upcoming_changes.md
@@ -1,3 +1,9 @@
+Next release dates:
+
+- Next CH EMED EPR version release: *TBD - early 2024*
+- Next aggregator deployment: *TBD - early 2024*
+
+
 Relevant changes from (upcoming) CH EMED EPR 1.0.0 based on CH EMED 4.0.0 (the latter should be published before the end of the current year):
 
   - Authorship and authorship timestamps. Please refer to the [CH EMED authorship guidance page](https://build.fhir.org/ig/hl7ch/ch-emed/authorship.html) for further reading:
@@ -28,4 +34,40 @@ Relevant changes from (upcoming) CH EMED EPR 1.0.0 based on CH EMED 4.0.0 (the l
   - Te CH EMED EPR IG reflects now that the `prescription` extension of the `MedicationDispense` resource is supported. 
 	- If the treatment has been prescribed, the aggregator's logic will continue to enforce that this extension is filled and that it references a valid prescription for the same treatment.
   - For all eMed resources, `note.time` shall not be supported any more: it is assumed that the time is the same as for the entry's authorship.
-	- With the exception of the PMLC `CHEMEDEPRMedicationStatementCard` that will continue to include `note.time` for each note.
+	- With the exception of the PMLC `CHEMEDEPRMedicationStatementCard` that will continue to include `note.time` for each note.
+
+
+Other aggregator changes:
+
+- `FindMedicationCard` queries will support the `ServiceStartFrom`, `ServiceStartTo`, `ServiceEndFrom`, `ServiceEndTo` parameters and apply them as follows:
+  - The aggregated start date of returned treatments must be between the specified `ServiceStartFrom` and `ServiceStartTo` parameters.
+    - If `ServiceStartFrom` is not specified, any treatment starting at or after the specified `ServiceStartTo` will meet the service start criterium.
+	- If `ServiceStartTo` is not specified,  any treatment starting before the specified `ServiceStartFrom` will meet the service start criterium.
+	- If neither `ServiceStartFrom` nor `ServiceStartTo` are specified, all treatments starting at any date will meet the service start criterium.
+	- Note that if a treatment does not have an explicit start date provided by a published document, it is assumed by the aggregator to be the date of creation of the MTP.
+  - The aggregated end date of returned treatments must be between the specified `ServiceEndFrom` and `ServiceEndTo` parameters.
+    - If `ServiceEndFrom` is not specified, any treatment ending at or after the specified `ServiceEndTo` will meet the service end criterium.
+	- If `ServiceEndTo` is not specified,  any treatment ending before the specified `ServiceEndFrom` will meet the service end criterium.
+	- If neither `ServiceEndFrom` nor `ServiceEndTo` are specified, all treatments ending at any date will meet the service end criterium.
+	- Note that if a treatment does not have an explicit end date provided by a published document, it is assumed by the aggregator to be *the end of time*, i.e. will have no end date.
+- Implementation of XDS `ServiceStartFrom`, `ServiceStartTo`, `ServiceEndFrom`, `ServiceEndTo` criteria for all ITI-18 and PHARM-1 queries.
+  - `PHARM-1 FindMedicationList` queries: same logic as for `FindMedicationCard`.
+  - `ITI-18` queries will match the criteria ranges against the stored metadata `XDSDocumentEntry.serviceStartTime` and `XDSDocumentEntry.serviceStopTime` as provided at ITI-41. See [date processing](transactions/date_processing.md).
+  - `PHARM-1` subqueries:
+    - `FindMedicationTreatmentPlans`, `FindMedicationList` and `FindMedicationCard` follow the same logic explained on the previous point.
+	- `FindPrescriptions`, `FindPrescriptionsForValidation` and `FindPrescriptionsForDispense` will apply the criteria against the prescription's validity period. 
+		- The prescription validy start date shall match if:
+			- Greater or equal than `ServiceStartFrom` if specified.
+			- Lesser than `ServiceStartTo` if specified.
+		- The prescription validty end date shall match if:
+			- Greater of equal than `ServiceEndFrom` if specified.
+			- Lesser than `ServiceEndTo` if specified.
+		- If a prescription does not specify a validity period start date, it is assumed to be the date of medical authorship (i.e. `authoredOn`).
+		- If a prescription does not specify a validity period end date, it is assumed to not have an end date and hence any specified *...To* parameter should match.
+	- `FindDispenses` will apply the criteria against a single date, which is the date of dispense (i.e. `whenHandedOver`).
+- Support for a new custom parameter for `FindMedicationCard` queries, `$PMLCIncludeNonActive` has been added. If specified and `true`, it will include all the (aggregated) treatments (constrained by the specified dates criteria) for the patient, whether they are active or not (i.e. it will include also suspended or cancelled treatments). These treatments will be included as medication statements in the content of the PMLC document but will not be added to the generated PDF. Support for this parameter is already included in the current snapshot (`2.1.2-SNAPSHOT`) of [Husky](https://github.com/project-husky/husky).
+
+
+!!! warning
+
+  Note that possible changes on Husky or other libraries/dependencies are not listed here and it is up to integrators to keep track of them.