Stream: implementers
Topic: logical models
Josh Mandel (Sep 05 2016 at 15:04):
I'm looking at @Eric Haas's "logical model" at http://ig.fhir.me/Healthedata1/OO-on-FHIR-Micro-Profile/microsusc-definitions.html#MicroSusc.gramstain and trying to understand how it maps to FHIR resources. [The model])(http://ig.fhir.me/Healthedata1/OO-on-FHIR-Micro-Profile/StructureDefinition-microsusc.json.html) says things like:
{ "id" : "MicroSusc.gramstain", "path" : "MicroSusc.gramstain", "short" : "Gram Stain", "definition" : "Gram stain observations that may be present for the culture panel.", "min" : 0, "max" : "*", "type" : [ { "code" : "Reference", "profile" : "http://hl7.org/fhir/us/lab/StructureDefinition/gs-obs" } ...
... but I don't see where this slots into the DiagnosticReport
resource: how is this "Gram Stain" element represented in FHIR, and how can I (or a tool) tell?
Josh Mandel (Sep 05 2016 at 15:06):
Also, the ]
seem to be missing from the .json.html
rendering I linked to -- not sure where that bug sits @Grahame Grieve
Grahame Grieve (Sep 05 2016 at 20:22):
I don't think Eric has done the formal mappings to DiagnosticReport yet - that one you reference will be an observation
Grahame Grieve (Sep 05 2016 at 20:24):
my bug.
Grahame Grieve (Sep 05 2016 at 20:40):
fixed. This will apply - and be fixed - in all IGs
Eric Haas (Sep 06 2016 at 00:47):
I kind of skipped or mashed some steps together. The entry point is a DiagnosticReport and the rest is the tree of Observations. This is essentially a guide on how to order the observation proifiles under a DR profile. I need to do a couple of mapping steps. to make it clearer
Eric Haas (Sep 06 2016 at 08:59):
@Josh Mandel Is this a clearer "logical model" I informally mapped profiles to it and I plan to create a structuremap, formally define all the profiles and make examples for each. ( the banner is me goofing around with the css).
Last updated: Apr 12 2022 at 19:14 UTC