Stream: implementers
Topic: Labresult how to implement
Stefan Scholte (Jan 10 2017 at 13:38):
I have a couple of question regarding lab results.
In HL7v2 a labresult consists of a ORC segment stating the ordering number the ordering provider etc.
and then a bunch of OBX segments each containing a code (e.g. Hemoglobine) and a Value (8.1 mmol/L)
this can be over 32 OBX'en
If I want to use FHIR resource(s) to resemble this.
I think one have to use a DiagnosticReport resource a DiagnosticOrder resource (referenced in DiagnosticReport) and 32 Observation resources (also referenced by DiagnosticReport). Am I correct?
But because of the 32 references, my client software, should do 32 requests to retrieve the observations. With performance in mind this is not desireable is it?
Are there any other "ways" to implement this?
Lloyd McKenzie (Jan 10 2017 at 16:59):
You might look at _include on the search page - you could retrieve the DiagnosticReport and _include the results in a single response. (Just be aware that paging is based on the number of reports returned, not the total number of records.)
Stefan Scholte (Jan 11 2017 at 11:09):
@Lloyd McKenzie but what should the server return if I use the _include search parameter (maybe a dumb question but I'm just starting implementing FHIR)
Lloyd McKenzie (Jan 11 2017 at 15:46):
With an _include, each page of results will also include the resources pointed to by the search set by the search criteria specified in the _include. So if you ask for "[base]/DiagnosticReport?.....&_include=result", you'll get entries for the first page of DiagnosticReports plus entries for all of the Observations pointed to by those DiagnosticReports. (If multiple DiagnosticReports on the page point to the same Observation, it'll only be included in the search set once. The entries corresponding to DiagnosticReport will have an entry.mode of "result" and the entries corresponding to Observation will have an entry.mode of "include".
Stefan Scholte (Jan 12 2017 at 13:37):
But should I use a Bundle or a Composition?
Lloyd McKenzie (Jan 12 2017 at 14:38):
Well, search results are always in a Bundle and documents are always in a Bundle. The real question is whether you want to put together a pre-defined package of everything which can then be shipped around, or you want people to query the piece or collection of pieces that are relevant to them based on relationships. There's also the question of whether you'll have a RESTful interface - you can pass documents around without one, but you obviously can't do REST without one.
Stefan Scholte (Jan 12 2017 at 15:55):
Thank you Lloyd for your answers, Perhaps I'm too much "burdened by HL7V2 way of thinking"
Last updated: Apr 12 2022 at 19:14 UTC
