hl7ch / ch-emed

FHIR Implementation Guide which defines the documents for the exchange of medication information in the context of the Swiss EPR
https://fhir.ch/ig/ch-emed/index.html
MIT License
0 stars 1 forks source link

CH EMED Organization (Quentin Ligier, ahdis) #294

Open ig-feedback opened 2 weeks ago

ig-feedback commented 2 weeks ago

ch.fhir.ig.ch-emed#5.0.0-ballot /StructureDefinition-ch-emed-organization.html

The organization address is required, most probably because it was required in the IPAG report (https://docs.google.com/spreadsheets/d/1Ui3NGFE2I8yiOlHELk-B0Pke2l9-Jbe5BTeYOnS8-uE/edit?gid=0#gid=0) In the EPR and the HPD, the address is not required. It's an issue for the PMP Portal, which creates Practitioner/PractitionerRole/Organization resources depending on the HPD content. It is unable to generate a valid document when the organization has no address in the HPD.

Quentin Ligier, ahdis

qligier commented 2 weeks ago

https://fhir.ch/ig/ch-emed/StructureDefinition-ch-emed-organization.html

ziegm commented 2 weeks ago

yes, the assumption of the origin of this requirement is correct.

@qligier will attend at the meeting on the 4.8.24 to discuss

dvribeira commented 2 weeks ago

Not sure how relevant this might be, but this is also mandatory on the eMediplan CHMED23A specs. Hence misaligning this now might be also a problem for the eMedication service and other systems that might have to support export to eMediplan.

image

qligier commented 2 weeks ago

Thanks @dvribeira, that is quite relevant! In CHMED16AF, it is not constrained, I'm not sure if both formats are supposed to be compatible.

https://chmed20af.emediplan.ch/fhir/StructureDefinition-chmed20af-card-composition.html

dvribeira commented 2 weeks ago

For what I have seen CHMED16A (eMediplan proper, not the FHIR translation) neither the practitioner nor the organization were modelled, the model in general being quite simpler than CHMED23A: imagem

The FHIR translation from CHMED23A is yet to be published, not sure if there is an updated ETA on this. An updated version of the print format should also be published at some point this year I believe, since it has been spun off the main spec document.

dvribeira commented 2 weeks ago

Given that this is a new constraint on the eMediplan specs and that maybe to some degree the new model has been updated to better accommodate translations to/from the FHIR version (pure speculation on my side), maybe on the eMediplan side they would agree on relaxing the constraint as well...

qligier commented 1 week ago

PJ OE QL SK IPAG defines the optionality of the organization address. It is required in the eMediplan. It is optional in the vaccination format, and more generally in the EPR.

The issue is kept open to gather feedback.

oliveregger commented 1 week ago

CHMED16A Revision 2 introduces also Organization for ePrescription: https://github.com/ig-emediplan/specification/pull/1/files