FHIR Chat · MedicationRequest with mandatory SNOMED medicationCode · conformance

Stream: conformance

Topic: MedicationRequest with mandatory SNOMED medicationCode


view this post on Zulip Kevin Mayfield (Jun 12 2020 at 08:52):

I'm wanting to mandate at least one SNOMED medication code in a MedicationRequest (R4).

I believe the best way of doing it is to create a profile on CodeableConcept (e.g. https://simplifier.net/electronicprescriptionservice/mandatorysnomedcodeableconcept)

Then the MedciationRequest is profiled to use this image.png

I would have liked to use a ValueSet but due to some terminology issues I can't at present.
It doesn't validate correctly at the moment but I think the definition is correct?

view this post on Zulip Jose Costa Teixeira (Jun 12 2020 at 09:03):

I can't understand well, but do you have a binding on medication[x]? should it not be on the medicationCodeableConcept?
And do you need a slice?

view this post on Zulip Kevin Mayfield (Jun 12 2020 at 09:28):

Tried to slice on medication[x] but it seemed awkward and caused some display errors.

view this post on Zulip Kevin Mayfield (Jun 12 2020 at 09:31):

I think I may have profiling issues in the image above

view this post on Zulip Kevin Mayfield (Jun 12 2020 at 09:53):

Cleaned parent profile
image.png
So this uses a profile on a 'child' datatype
image.png

view this post on Zulip Jose Costa Teixeira (Jun 12 2020 at 11:04):

I think medication[x] in R4 is 1..1, how do you have 0..* ?

view this post on Zulip Jose Costa Teixeira (Jun 12 2020 at 11:05):

what do you want to achieve?

  • people can only use SCT codes?
  • people can use SCT or other codes, but at least one SCT is mandatory?
    ...?

view this post on Zulip Kevin Mayfield (Jun 13 2020 at 04:07):

The later, the service needs one SCT. It will not reject other codes in the resource. (be tolerant).
(Secondary issue - the SCT needs to come from a ValueSet but we have issues around terminology)


Last updated: Apr 12 2022 at 19:14 UTC