Fixed build URLs for normal ones and CH-EMED-EPR with CH EMED EPR

dvribeira · dvribeira · commit 5bc6bb6dba75 · 2025-03-31T11:45:53.000+02:00
diff --git a/docs/emed/index.md b/docs/emed/index.md
@@ -1,9 +1,8 @@
-# CH-EMED-EPR
+# CH EMED EPR
 
-CH-EMED-EPR is a FHIR equivalent to CDA-CH-EMED.
-Its specification are entirely described in [https://build.fhir.org/ig/CARA-ch/ch-emed-epr/](https://build.fhir.org/ig/CARA-ch/ch-emed-epr/).
+[CH EMED EPR](https://fhir.ch/ig/ch-emed-epr/index.html) is a FHIR implementation guide that specifies mostly the eMedication service's exchange format.
 
-It is built upon [CH-EMED](http://build.fhir.org/ig/hl7ch/ch-emed/) (the Swiss eMedication profile), [CH-CORE](https://build.fhir.org/ig/hl7ch/ch-core/) and [CH-Term](http://fhir.ch/ig/ch-term/index.html).
+It is built upon [CH EMED](https://fhir.ch/ig/ch-emed/index.html) (the Swiss eMedication profile), [CH CORE](https://fhir.ch/ig/ch-core/index.html) and [CH Term](http://fhir.ch/ig/ch-term/index.html).
 In particular, CH-EMED contains a lot of documentation about the use of the profile, it is highly recommended reading it.
 
 !!! tip
diff --git a/docs/index.md b/docs/index.md
@@ -4,7 +4,7 @@ Welcome to the Integration Guide for the eMedication service of CARA's community
 
 * [Transactions](transactions/index.md): information about the implemented transactions.
 * [Workflows](workflows/index.md): description of the different workflows clients of this service can follow.
-* [CH-EMED-EPR](emed/index.md): description of the eMedication [file format](https://build.fhir.org/ig/CARA-ch/ch-emed-epr/).
+* [CH EMED EPR](emed/index.md): description of the eMedication [exchange format](https://fhir.ch/ig/ch-emed-epr/index.html).
 * [PMP-APPC](appc/index.md): description of the policy file format.
 * [OIDs](oids.md): relevant OIDs to be used within the scope of the eMedication service.
 * [Endpoints](endpoints.md): the eMedication service endpoints available to clients.
@@ -14,7 +14,7 @@ Welcome to the Integration Guide for the eMedication service of CARA's community
 
 - Issues or suggestions about this guide can be reported on the [guide's GitHub](https://github.com/CARA-ch/emed-service-guide/issues).
 - Issues or suggestions about the eMedication service can be reported [here](https://github.com/CARA-ch/pmp-issues/issues).
-- [CH-EMED-EPR issues](https://github.com/CARA-ch/ch-emed-epr/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc)
+- [CH EMED EPR issues](https://github.com/CARA-ch/ch-emed-epr/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc)
 
 ## Other Resources
 
@@ -23,7 +23,7 @@ Welcome to the Integration Guide for the eMedication service of CARA's community
 	* [IPF code](https://github.com/oehf/ipf): IPF provides an Apache Camel implementation of pretty much all transactions
   used in the Swiss EPR.
 	* [IPF documentation](https://oehf.github.io/ipf-docs/)
-* Husky: Health Usability Key - convenience API for IHE transactions and CDA documents, as well as CH-EMED-EPR related FHIR.
+* Husky: Health Usability Key - convenience API for IHE transactions and CDA documents, as well as CH EMED EPR related FHIR.
 	* [Husky code](https://github.com/project-husky/husky)
 	* [Husky javadoc](https://project-husky.github.io/husky/)
 	* [Husky wiki](https://github.com/project-husky/husky/wiki)
diff --git a/docs/transactions/documents.md b/docs/transactions/documents.md
@@ -2,7 +2,7 @@
 
 ## Content
 
-The eMedication service only support [PMP-APPC](../appc/index.md) and [CH-EMED-EPR](../emed/index.md) documents.
+The eMedication service only support [PMP-APPC](../appc/index.md) and [CH EMED EPR](../emed/index.md) documents.
 
 ## Metadata
 
diff --git a/docs/transactions/iti41.md b/docs/transactions/iti41.md
diff --git a/docs/transactions/iti43.md b/docs/transactions/iti43.md
@@ -8,7 +8,7 @@ See also [EPD by example's Retrieve Document Set](https://github.com/ehealthsuis
 
 ## On-demand documents
 
-Generation rules for CH-EMED-EPR [PML (Medication List)](https://build.fhir.org/ig/CARA-ch/ch-emed-epr/document_pml.html) and [PMLC (Medication Card)](https://build.fhir.org/ig/CARA-ch/ch-emed-epr/document_pmlc.html) documents are described in the [CH-EMED-EPR IG](https://build.fhir.org/ig/CARA-ch/ch-emed-epr/).
+Generation rules for CH EMED EPR [PML (Medication List)](https://fhir.ch/ig/ch-emed-epr/document_pml.html) and [PMLC (Medication Card)](https://fhir.ch/ig/ch-emed-epr/document_pmlc.html) documents are described in the [CH EMED EPR IG](https://fhir.ch/ig/ch-emed-epr/).
 
 ## Error codes
 
diff --git a/docs/transactions/iti57.md b/docs/transactions/iti57.md
@@ -6,7 +6,7 @@ The [ITI-57 (Update Document Set)](https://www.ihe.net/uploadedFiles/Documents/I
 
 This transaction is implemented, but only for the *deletionStatus* attribute. This implies that the only possible update in the service is the deletion of a document.
 
-### Deleting a CH-EMED-EPR document
+### Deleting a CH EMED EPR document
 The rules are similar to [ITI-41](iti41.md) replacement.
 
 * Patient / representative can only request the removal of a document published by the same patient. Hence a patient cannot request the removal of a document published by a healthcare professional.
@@ -15,18 +15,18 @@ The rules are similar to [ITI-41](iti41.md) replacement.
 	  * Deletion rights related to HCP are not implemented yet and will be subject to further discussion before implementation. For now, patients are allowed to delete documents provided by HCPs and HCPs are not allowed to delete any documents.
 * Document administrator may only request the removal of any document published by either a patient, representative, or healthcare professional.
 * Only approved documents at the end of a treatment chain can be requested to be deleted.
-* Requested deletion of a CH-EMED-EPR document will also flag for deletion the chain of replaced documents by this document, if it exists.
+* Requested deletion of a CH EMED EPR document will also flag for deletion the chain of replaced documents by this document, if it exists.
 * Documents to be deleted must exist in the repository.
 * Currently the service just permanently deletes the requested documents, no archival or flagging is done.
 
 ### Deleting an APPC document
-* Deleting an [APPC](https://www.ihe.net/uploadedFiles/Documents/ITI/IHE_ITI_Suppl_APPC.pdf) document means that the patient is opting out. It triggers an archive and removal of all the documents for this patient: [CH-EMED-EPR](https://build.fhir.org/ig/CARA-ch/ch-emed-epr/) and APPC (including and any deprecated ones) documents are both concerned.
+* Deleting an [APPC](https://www.ihe.net/uploadedFiles/Documents/ITI/IHE_ITI_Suppl_APPC.pdf) document means that the patient is opting out. It triggers an archive and removal of all the documents for this patient: [CH EMED EPR](https://fhir.ch/ig/ch-emed-epr/) and APPC (including and any deprecated ones) documents are both concerned.
 * Only the patients or their representatives can request the deletion of their own APPC documents.
 * A policy administrator can request the removal of any patient's APPC of their own reference community.
 * The APPC document has to be approved
     * This implies that direct deletion of a deprecated (replaced) APPC document is not possible.
     * Unapproved APPC document deletion can only occur at opt-out.
-* Currently the service just permanently deletes the requested APPC document and all the CH-EMED-EPR documents and any other information stored by the PMP concerning this patient, no archival or flagging is done.
+* Currently the service just permanently deletes the requested APPC document and all the CH EMED EPR documents and any other information stored by the PMP concerning this patient, no archival or flagging is done.
 
 ## Update DocumentEntry availabilityStatus
 
diff --git a/docs/workflows/aggregation.md b/docs/workflows/aggregation.md
@@ -3,9 +3,9 @@
 |Term|Definition|References|
 |----|----------|----------|
 |Medication plan (current medication)|The medication plan is the documentation of all the medication information for a patient at a certain point of time.<br/>The medication plan can be presented as a [medication card](https://github.com/ehealthsuisse/EPD-by-example/blob/main/files/MedicationCardDocument.md) or as an [eMediplan](https://emediplan.ch/) (eMediplan is not supported by the service, it is another way of displaying the medication plan).|See [IHE Pharmacy Community Medication List (PML)](https://www.ihe.net/uploadedFiles/Documents/Pharmacy/IHE_Pharmacy_Suppl_PML.pdf) and IPAG's definition ([FR](https://www.fmh.ch/files/pdf24/rapport-gtip-ipag-sur-la-cybermedication.pdf), [DE](https://www.fmh.ch/files/pdf24/ipag-bericht-emedikation.pdf)), § 2.1 and § 2.5.|
-|Medication treatment|A medication treatment corresponds to one single medication the patient was planned to take in the past or is planned to take presently or in the future, including its name, dosage, frequency of intake, etc.<br/>Medication treatments are created every time an [MTP document](https://build.fhir.org/ig/CARA-ch/ch-emed-epr/document_mtp.html) is received.<br/> This service considers two kinds of medication treatments: "simple" and "prescribed".<br/> Simple medication treatments are created with just one [MTP document](https://build.fhir.org/ig/CARA-ch/ch-emed-epr/document_mtp.html) (by the patient or a healthcare professional).<br/> Prescribed medication treatments are created by healthcare professionals only, with an [MTP document](https://build.fhir.org/ig/CARA-ch/ch-emed-epr/document_mtp.html) followed by a [PRE document](https://build.fhir.org/ig/CARA-ch/ch-emed-epr/document_pre.html).|See [IHE Pharmacy MTP supplement](https://www.ihe.net/uploadedFiles/Documents/Pharmacy/IHE_Pharmacy_Suppl_MTP.pdf), as well as [HL7's Medication Treatment Plan FHIR document](https://build.fhir.org/ig/hl7ch/ch-emed//medication-treatment-plan-document.html).|
-|Medication treatment instance|A medication treatment instance is a concept of this eMedication service.<br/>  A medication treatment can change over time: the dosage, medication, active substance, comments, etc. can be updated.<br/> The medication treatment instance represents the state of a medication at a current point of time. <br/>Medication treatment instance creation depends on the type of medication treatment. For "simple" (ie. not prescribed) treatments, a single medication treatment instance is created when the [MTP document](https://build.fhir.org/ig/CARA-ch/ch-emed-epr/document_mtp.html) is received. <br/> For _prescribed_ medication treatments (ie. medication treatments for which there is a [MTP document](https://build.fhir.org/ig/CARA-ch/ch-emed-epr/document_mtp.html) and at least one  [PRE document](https://build.fhir.org/ig/CARA-ch/ch-emed-epr/document_pre.html)), a new instance is created every time a [PRE document](https://build.fhir.org/ig/CARA-ch/ch-emed-epr/document_pre.html) is received.<br/>Each medication treatment instance appears in a single line within the medication card. Instances associated with the same treatment are visually grouped.|-|
-|Medication statement|A medication statement represents a given medication (form, dosage, GTIN/ATC, ingredients etc.)|See the [definition in the implementation guide](https://build.fhir.org/ig/CARA-ch/ch-emed-epr/StructureDefinition-ch-emed-epr-medicationstatement-treatmentplan.html).|
+|Medication treatment|A medication treatment corresponds to one single medication the patient was planned to take in the past or is planned to take presently or in the future, including its name, dosage, frequency of intake, etc.<br/>Medication treatments are created every time an [MTP document](https://fhir.ch/ig/ch-emed-epr/document_mtp.html) is received.<br/> This service considers two kinds of medication treatments: "simple" and "prescribed".<br/> Simple medication treatments are created with just one [MTP document](https://fhir.ch/ig/ch-emed-epr/document_mtp.html) (by the patient or a healthcare professional).<br/> Prescribed medication treatments are created by healthcare professionals only, with an [MTP document](https://fhir.ch/ig/ch-emed-epr/document_mtp.html) followed by a [PRE document](https://fhir.ch/ig/ch-emed-epr/document_pre.html).|See [IHE Pharmacy MTP supplement](https://www.ihe.net/uploadedFiles/Documents/Pharmacy/IHE_Pharmacy_Suppl_MTP.pdf), as well as [HL7's Medication Treatment Plan FHIR document](https://fhir.ch/ig/ch-emed/medication-treatment-plan-document.html).|
+|Medication treatment instance|A medication treatment instance is a concept of this eMedication service.<br/>  A medication treatment can change over time: the dosage, medication, active substance, comments, etc. can be updated.<br/> The medication treatment instance represents the state of a medication at a current point of time. <br/>Medication treatment instance creation depends on the type of medication treatment. For "simple" (ie. not prescribed) treatments, a single medication treatment instance is created when the [MTP document](https://fhir.ch/ig/ch-emed-epr/document_mtp.html) is received. <br/> For _prescribed_ medication treatments (ie. medication treatments for which there is a [MTP document](https://fhir.ch/ig/ch-emed-epr/document_mtp.html) and at least one  [PRE document](https://fhir.ch/ig/ch-emed-epr/document_pre.html)), a new instance is created every time a [PRE document](https://fhir.ch/ig/ch-emed-epr/document_pre.html) is received.<br/>Each medication treatment instance appears in a single line within the medication card. Instances associated with the same treatment are visually grouped.|-|
+|Medication statement|A medication statement represents a given medication (form, dosage, GTIN/ATC, ingredients etc.)|See the [definition in the implementation guide](https://fhir.ch/ig/ch-emed-epr/StructureDefinition-ch-emed-epr-medicationstatement-treatmentplan.html).|
 |Aggregation|The aggregation is the process of determining the current state of each medication treatment within a patient's medication plan, based on the existing medication treatment instances.<br/>This is done depending on the document triggering the aggregation, either by updating existing medication treatments /  medication treatment instances, or by creating new medication treatment instances|-|
 
 ## Triggers
@@ -18,7 +18,7 @@ Aggregation occurs when:
 ## Scope
 When triggered, aggregation occurs for the medication treatment referenced by the triggering document.
 
-When the triggering document is a [PRE](https://build.fhir.org/ig/CARA-ch/ch-emed-epr/document_pre.html), it might reference several medication treatments (multi-prescription). In this case the service applies the aggregation process to each referenced medication treatment.
+When the triggering document is a [PRE](https://fhir.ch/ig/ch-emed-epr/document_pre.html), it might reference several medication treatments (multi-prescription). In this case the service applies the aggregation process to each referenced medication treatment.
 
 ## Aggregation process
 ### Overview
diff --git a/docs/workflows/situationalworkflows.md b/docs/workflows/situationalworkflows.md
diff --git a/mkdocs.yml b/mkdocs.yml
