Stream: implementers
Topic: Stu2/R3 mapping
David Hay (May 07 2018 at 01:43):
Got a question about Patient.contact.relationshipRole (and which could apply in other mapping scenarios between R2 & 3).
The valueset changed between R2 & R3, so what's the best practice when a 'R2' value is more specific than the R3 value. eg in the R2 valueset we have 'parent' - which would match to 'N' (Next of Kin). in R3 - but we lose the detail about being a parent. The element datatype is a CodeableConcept with an extensible binding.
we could:
1) accept the loss of specificity
2) continue to use the r2 codesystem
3) place both values in the CC...
4) use the R3 value with an extension
thoughts?
Fernando Mayoral (May 08 2018 at 21:57):
looks like there are no thoughts on this, we will probably go for using both values as it doesn't seem conflicting, at least not a first glance
Grahame Grieve (May 09 2018 at 04:24):
I guess that's the intent. @Cooper Thompson ?
Last updated: Apr 12 2022 at 19:14 UTC
