Stream: clinFHIR
Topic: StructureDefinition for a FHIR Document
John Moehrke (Mar 01 2018 at 16:20):
David, does clinFHIR support profiling a document? If so, is there some instructions (video) on how to do it?
David Hay (Mar 01 2018 at 17:26):
sorry, no it doesn't... :(
David Hay (Mar 01 2018 at 17:27):
How would you see it working if it were to do so?
John Moehrke (Mar 01 2018 at 17:30):
So, a Document first needs to be assembled out of the various Resources... one of these, two of those, many of these other things...
John Moehrke (Mar 01 2018 at 17:30):
seemed like the thing clinFHIR does well
John Moehrke (Mar 01 2018 at 17:31):
then the task of doing element level profiling of each of those resouces...
David Hay (Mar 01 2018 at 19:26):
so you can create a document - see https://fhirblog.com/creating-a-fhir-document/
and no reason why the individual resource instances could't be profile instances (though there are issues with complex extensions - and extensions that are not at the resource root at the moment)...
John Moehrke (Mar 01 2018 at 19:41):
I have no interest in playing with extensions...
David Hay (Mar 01 2018 at 19:46):
so what would the profiling of the associated resources entail?
John Moehrke (Mar 01 2018 at 20:02):
setting specific content expectations. not all profiling is about extending FHIR.. some of us are very happy with what is there, we just want it to be more specific.
David Hay (Mar 01 2018 at 20:03):
so different ValueSets for example, and removing fields that aren't needed for a use Case?
John Moehrke (Mar 01 2018 at 20:04):
yup.
David Hay (Mar 01 2018 at 20:04):
That should all work OK...
David Hay (Mar 01 2018 at 20:04):
Let me know how you get on!
John Moehrke (Mar 01 2018 at 20:05):
I will poke around given your instructions...
Last updated: Apr 12 2022 at 19:14 UTC
