Extension EPR Time - Add MedicationRequest.requester to context

[dvribeira]

As per the subject, MedicationRequest.requester is missing from the context in input/fsh/extensions/EPRTime.fsh

[ziegm]

@dvribeira thanks for your input and your PR. Do you mean because of the description in CH EMED?
http://fhir.ch/ig/ch-emed/different-authors.html

[dvribeira]

@ziegm Yes it is related to that. I have another discussion that I have not yet found the time to trigger concerning the different authorships (document and medical) and their timestamps and how to manage them. But they belong to the CH-EMED project. I can already comment them here in case it adds any value to the issue:
The guidance in CH-EMED establishes that:

1. There is indeed a difference to be supported between a document author and a medical author.
2. Authorship is to be provided:
   • Within the composition (composition.author and, if different, composition.section.author) for provided documents and not within entries.
   • Within the entries (e.g. MedicationStatement.informationSource and, if different, MedicationStatement.extension.authorDocument) for PML and PMLC documents.

Furthermore we draw the conclusion that authorship differs also if authorship timestamp differs and that this is to be supported with the references from:

• The IHE profiles: https://www.ihe.net/uploadedFiles/Documents/Pharmacy/IHE_Pharmacy_Suppl_MTP.pdf
  
• The time extension is specified explicitly for composition.author and for the documentAuthor extension.

I assumed the time extension could be used for all the informationSource equivalent elements of the entries and that would allow us to implement the authorship as described in the guidelines also taking into account authorship timestamp in a coherent and intuitive manner.

The alternatives would be to:

• Not consider authorhip timestamp but then I guess we should just use document timestamp and composition.author and documentAuthor have no need to display the time extension.
• Use fields already present in the entries, for instance whenHandedOver. But this poses the question regarding why don't we use them when providing a document. Furthermore I am not sure whether these fields cannot have other more specific semantics attached.

[ziegm]

30.08.2023:
12-0-0