Stream: implementers
Topic: Mapping of target data management context
Florian Wolf (Dec 14 2021 at 08:37):
Hello community,
I have an analysis question regarding the available attributes of a FHIR Diagnostic Report and how that fits to our system concepts. We want to provide the possibility to store Diagnostic Reports in our system in different logical units representing the organizational structure of a clinical institution. This serves as a kind of data management context.
Since this information is not a direct property of a single Diagnostic Report we thought of the meta element.
The source information of the meta element allow us to properly identify the sending application. What we are missing is where we could require to provide the information about this logical unit to store the Diagnostic Report within. We thought of defining an own extension for the meta element. Actually I just need a name to identify the proper data management context. I wonder, if anyone has concerns about such an approach or any other idea how to best transmit this kind of information?
Thanks in advance.
Grahame Grieve (Dec 14 2021 at 08:44):
it looks like what DiagnosticReport.category is intended for to me
Florian Wolf (Dec 14 2021 at 08:55):
Thanks for the quick response @Grahame Grieve .
That was also our first intention. But thinking of supporting additional resources (where we face the same issue) that doesn't scale. Like e.g. DocumentReference.category has a complete different meaning.
Last updated: Apr 12 2022 at 19:14 UTC
