Closed dvribeira closed 3 months ago
I don't know why it was restricted, but I would be inclined to think it was done to have at most one reasonCode.text
.
PMP Specs Meeting: O. Egger commented the source of this cardinality constraint was the IPAG domain definition: https://docs.google.com/spreadsheets/d/1Ui3NGFE2I8yiOlHELk-B0Pke2l9-Jbe5BTeYOnS8-uE
Could be reviewed if needed.
The issue has not been further discussed given no person present from affected systems. See meeting notes: https://docs.google.com/document/d/1af-pNhEVU2IbAHV0opZwPCJC0bORCwQOlKG_0oGgwfQ
@dvribeira To be discussed at the next SPEC meeting (April 24th) for multiple reason code
After meeting with professionals on 2024.04.30: a request to change the cardinality to 0..* will be submitted.
CH EMED request: https://github.com/hl7ch/ch-emed/issues/268
The cardinality has been changed per our request in CH EMED (pending publication of new release) and will be integrated by CH EMED EPR with the next publication (shortly after CH EMED's in principle).
After discussion with @dejajs , concerning Presco's mapping of their own treatments, Presco allows specifying several treatment reasons (several coded and one as a free text IIUC), which is not allowed with the current cardinality (constrained by CH EMED to 0..1). The reasons for this predate my arrival to the project so I do not know if there was some reason other than simplicity for this constraint.
@qligier Do you have any recollection about why
MedicationStatement.reasonCode
has cardinality0..1
on the MTP document? We can discuss this tomorrow during the PMP specs meeting.