Stream: implementers
Topic: Extending a Reference List
Mike Hamidi (Apr 07 2022 at 15:43):
Are there any rules on extending an existing "Reference" list? For example, in R4 AdverseEvent.subjectMedicalHistory , can the "Reference(Condition | Observation | AllergyIntolerance | FamilyMemberHistory | Immunization | Procedure | Media | DocumentReference)" be extended to also cover "Medication"? Note: In this use case a medication that does not fall under AdverseEvent.suspectEntity
Jean Duteau (Apr 07 2022 at 15:54):
Adding the Medication wouldn't make sense in this case because it doesn't have tell you how that Medication was used. Adding MedicationStatement or MedicationAdministration would make sense.
Mike Hamidi (Apr 07 2022 at 16:02):
Thanks @Jean Duteau So, technically speaking, you can add those resources?
Jean Duteau (Apr 07 2022 at 16:03):
if you are using the R4 resource, you wouldn't be able to send one of those resources since it would be invalid. You can send them in as an extension to that element if needed. If you are suggesting making a change to the R4 resource, i.e. to add new capability in R5, then yes it can technically be done.
Mike Hamidi (Apr 07 2022 at 16:06):
So an extension element to AdverseEvent.subjectMedicalHistory to include Reference(MedicationStatement | MedicationAdministration). We may be requesting this as part of the Vulcan AdverseEvent track (TBD).
Jean Duteau (Apr 07 2022 at 16:11):
yes, that would be how you would include it in a profile on the R4 resource.
Mike Hamidi (Apr 07 2022 at 16:14):
Thank you!
Lloyd McKenzie (Apr 07 2022 at 16:28):
As always, if you think a particular resource in a given version is missing something, before you try to work around with extensions:
- Check to see if the issue has been addressed in the CI-build. If it has, you can use the standard inter-version extension mechanism
- Otherwise, raise the use-case on the appropriate stream here. It may be that there's another 'better' way to solve the problem. (And if not, it may lead to a request to change the specification for future releases, which then opens up #1 as an option for you.)
Last updated: Apr 12 2022 at 19:14 UTC
