Stream: implementers
Topic: Procedure laterality (without post coordination)
Richard Kavanagh (Jul 15 2021 at 09:17):
We are exploring how we expose a source of clinical procedure data in FHIR. This particular source holds "body site" and "laterality" in an uncoded form (or as poorly managed codes). We could concatenate the two into a single string to place in Procedure.bodysite.text but this reduces the fidelity of the data and only works in one direction.
Where we have data sources using SNOMED then I understand the expectation is to use post coordination (which has different issues!) but for scenarios where this is not possible is there a consistent approach?
Lloyd McKenzie (Jul 15 2021 at 14:04):
You can use BodyStructure - either as an independent identified instance or as a contained resource.
Lloyd McKenzie (Jul 15 2021 at 14:04):
In some cases there are also extensions available
Richard Kavanagh (Jul 15 2021 at 15:29):
Thanks @Lloyd McKenzie - presumably when using BodyStructure it would have to be via an extension as It is not referenced from procedure itself.
Lloyd McKenzie (Jul 15 2021 at 15:31):
Correct. There is, however, a standard extension. (The belief is that, right now, we don't have wide support in systems for more than a simple code - tracking detailed locations or tying observations and procedures to specific tumors, lesions, fetuses, etc. is 'advanced' functionality that properly lives in extension space. If you don't think that's accurate, you can always file a change request :smile: )
Richard Kavanagh (Jul 15 2021 at 15:34):
Thats fine - thanks @Lloyd McKenzie . The Extension route will be fine for now.
Last updated: Apr 12 2022 at 19:14 UTC
