#3 add short description ot XUA, HPD and ATNA profiles and useful tra… (

#30) * #3 add short description ot XUA, HPD and ATNA profiles and useful transactions * #3 add references to epd by example
CARA-ch · Oct 12, 2023 · 56df6c5 · 56df6c5
1 parent 4f344a8
commit 56df6c5
Show file tree

Hide file tree

Showing 4 changed files with 23 additions and 1 deletion.
diff --git a/docs/transactions/index.md b/docs/transactions/index.md
@@ -45,3 +45,19 @@ Even though the eMedication service doesn't support it yet, it is possible to us
 |---------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|
 | XDSRegistryError    | In case of business rule error, missing/invalid XUA (authentication errors), unexpected exception.                                                  |
 | XDSUnknownPatientId | If the patient ID is unknown (i.e. the patient has not registered), if the subjects is missing rights to preform the action (authorization errors). |
+
+## Other transactions
+In addition to the [XDS](https://profiles.ihe.net/ITI/TF/Volume1/ch-10.html) transactions implemented by the service, implementers may find it useful to check out the following profiles and transactions :
+* [Cross Enterprise User Assertion (XUA)](https://profiles.ihe.net/ITI/TF/Volume1/ch-13.html) profile, and the [Provide X-User Assertion (XUA ITI-40)](https://profiles.ihe.net/ITI/TF/Volume2/ITI-40.html#3.40) transaction.
+    * The XUA profile defines the format of assertions inserted in transactions, that contain information about the users and their roles.
+    * The ITI-40 transaction is used to obtain the assertions from an assertion provider.
+* [Healthcare Provider Directory (HPD)](https://www.ihe.net/uploadedFiles/Documents/ITI/IHE_ITI_Suppl_HPD.pdf) profile, and the [Provider Information Query (HPD ITI-58)](https://profiles.ihe.net/ITI/TF/Volume2/ITI-58.html) transaction.
+    * The HPD profile defines the management of healthcare provider information in a directory structure.
+    * The ITI-58 transaction can be used to lookup healthcare provider information from a healthcare provider directory.
+* [Audit Trail and Node Authentication (ATNA)](https://profiles.ihe.net/ITI/TF/Volume1/ch-9.html) profile, and the [record audit event (ATNA ITI-20)](https://profiles.ihe.net/ITI/TF/Volume2/ITI-20.html#3.20) transaction.
+    * The ATNA profile might be used by implementers to record audit events through the ITI-20 transaction.
+
+The [EPD-by-example](https://github.com/ehealthsuisse/EPD-by-example/) github project provides guidance and examples about these transactions and others, especially :
+* [Get X-User Assertion](https://github.com/ehealthsuisse/EPD-by-example/blob/main/files/GetXAssertion.md) and [Provide X-User Assertion](https://github.com/ehealthsuisse/EPD-by-example/blob/main/files/ProvideXAssertion.md)
+* [Authenticate User](https://github.com/ehealthsuisse/EPD-by-example/blob/main/files/AuthenticateUser.md)
+* [PIX Query](https://github.com/ehealthsuisse/EPD-by-example/blob/main/files/PIXQuery.md)
diff --git a/docs/transactions/iti18.md b/docs/transactions/iti18.md
@@ -4,6 +4,8 @@ The [ITI-18 (Registry Stored Query)](https://profiles.ihe.net/ITI/TF/Volume2/ITI
 
 This transaction has been implemented in order to respect the Swiss EPR regulation. However, it is very generic, and [CH:PHARM-1](chpharm1.md) should be favored, as it offers emedication-specific query parameters.
 
+See also [EPD by example's Registry Stored Query](https://github.com/ehealthsuisse/EPD-by-example/blob/main/files/AuthenticateUser.md) page.
+
 ## Stored queries
 ### Generic rules
 * Folders option not supported

diff --git a/docs/transactions/iti41.md b/docs/transactions/iti41.md
@@ -2,7 +2,9 @@
 
 The [ITI-41 (Provide and Register Document Set-b)](https://profiles.ihe.net/ITI/TF/Volume2/ITI-41.html) transaction allows a [content sender](https://profiles.ihe.net/ITI/TF/Volume2/ITI-41.html#3.41.2) to send documents to the eMedication service ([content receiver](https://profiles.ihe.net/ITI/TF/Volume2/ITI-41.html#3.41.2)). 
 
-Generic [DocumentEntry metadata](https://profiles.ihe.net/ITI/TF/Volume3/ch-4.2.html#4.2.1.1) are described in the [documents section](documents.md). This page references additional constraints specific to ITI-41. See also IHE's documentation for [metadata in Document Sharing profiles](https://profiles.ihe.net/ITI/TF/Volume3/index.html).
+Generic [DocumentEntry metadata](https://profiles.ihe.net/ITI/TF/Volume3/ch-4.2.html#4.2.1.1) are described in the [documents section](documents.md). This page references additional constraints specific to ITI-41. 
+
+See also IHE's documentation for [metadata in Document Sharing profiles](https://profiles.ihe.net/ITI/TF/Volume3/index.html) as well as [EPD by example's Provide and Register Document Set](https://github.com/ehealthsuisse/EPD-by-example/blob/main/files/ProvideAndRegister.md) page.
 
 ## Publishing documents
 ### Document types

diff --git a/docs/transactions/iti43.md b/docs/transactions/iti43.md
@@ -4,6 +4,8 @@ The [ITI-43 (Retrieve Document Set)](https://profiles.ihe.net/ITI/TF/Volume2/ITI
 
 This transaction, implemented as per the specifications. All documents are retrievable with an ITI-43 transaction (with the proper access rights : only patients, representatives and policy administrators can retrieve [APPC (Advanced Patient Privacy Consent)](https://www.ihe.net/uploadedFiles/Documents/ITI/IHE_ITI_Suppl_APPC.pdf) documents).
 
+See also [EPD by example's Retrieve Document Set](https://github.com/ehealthsuisse/EPD-by-example/blob/main/files/RetrieveDocumentSet.md) page.
+
 ## 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/).