Stream: clinFHIR
Topic: logical modeller
David Hay (Mar 31 2017 at 18:33):
Hi Jayashree - the modeller can be used in a number of ways, and the answer about the element mapping depends on what you're wanting to achieve. I assume that you are wanting to build a simple profile based on Patient and started with a 'single resource' (Patient) when you created the model.
When you add an 'occupation' element to the logical model and subsequently generate a profile, it will be represented in the profile as an extension, so what you need to do is first create the extension definition and bind it to the ValueSet (there’s a module in CF that does that), then set the fhir mapping in the model element to 'Patient.extension' and a button will be displayed that allows you to select that extension.
When you subsequently generate the profile (select the Model tab at the top right, then click the ‘Generate Profile’ link bottom right) the profile will be correctly ‘wired up’ to the extension definition.
If you aren’t interest in generating profiles, and just want to represent a model – say as part of a design process – then you can just ignore the mapping. In that case you’d bind the element to the ValueSet (as you did) so that it would show correctly when using the Logical Model in the Scenario Builder (see https://vimeo.com/200105501 )
Jayashree Surnar (Apr 07 2017 at 04:11):
Thank you very much @David Hay , i will try.
Jayashree Surnar (Apr 07 2017 at 04:18):
while creating the extension what datatype should i choose code or codeableconcept or coding?
Jayashree Surnar (Apr 07 2017 at 09:50):
hello @David Hay , here under communication language is not there.
David Hay (Apr 07 2017 at 18:52):
Dang - I strip out the 'meta' elements to de-clutter to the resource types. Looks like that will need to go back in.
David Hay (Apr 07 2017 at 19:17):
wrt coding / code / CC - the advice generally is that if there is a fixed set of values that won't change (preferably small) then code is OK. Otherwise use CodeableConcept. Coding is uncommon.
David Hay (Apr 07 2017 at 19:24):
Just looking into this - there isn't a language element in Communication. I'm not that familiar with the base Resource.language element, but assuming that you want to be able to indicate in what language you what the communication to occur, then I don't think that Resource.language is the correct element to use. For example Patient has a specific element for language - in the case of communication you'd need an extension...
Jayashree Surnar (Apr 10 2017 at 05:17):
thank you @David Hay , can you see this once?lang.PNG here in base resource under communication language is there but in clinfhir it's not there so if create profile using clinfhir it will not get that right so what should i do can you please suggest me? sorry if you are not getting what i'm saying.
David Hay (Apr 10 2017 at 06:32):
Ah - my bad, I thought you were referring to the Communication resource! So this is being accidentally stripped out - I will try to rectify shortly... (in the next 24 hours that is). Will post here when done...
David Hay (Apr 10 2017 at 07:07):
Ok - so I had a bit of spare time so I made the fix. This only applies to new models of course - for existing models just add it back in...
Jayashree Surnar (Apr 10 2017 at 08:31):
@David Hay thank you.
Jayashree Surnar (Apr 11 2017 at 04:01):
hello @David Hay , can you please see my patient profile(Patientvms) once?have created in clinfhir (Public HAPI STU3 server).
David Hay (Apr 11 2017 at 04:49):
yep - all seems to be there!
Jayashree Surnar (Apr 11 2017 at 05:00):
thank you. @David Hay
i have one more doubt, i want to add age to patient, so what is the better way? whether to create an extension called age and map it to patient.extension? or just add as an element and map it to patient.text and then generate a profile? please let me know.
Jayashree Surnar (Apr 11 2017 at 10:33):
.
Lloyd McKenzie (Apr 11 2017 at 14:48):
Given that resources can be stored for a long time and that age is a point-in-time calculation, be cautious about adding it as an extension on Patient. (It makes more sense to add it on point-in-time assessments like Observation or Procedure.)
David Hay (Apr 11 2017 at 17:35):
Thanks lloyd! For something that is so easily calculated, it doesn't make a lot of sense to add to the resource - and anyway, presumably the age is in connection with something else - "the asthma started at age 10"...
David Hay (Apr 11 2017 at 17:36):
As a corollary it can be surprisingly tricky getting extensions right!
Rob Hausam (Nov 04 2018 at 21:22):
(deleted)
Rob Hausam (Nov 04 2018 at 21:38):
(deleted)
Lloyd McKenzie (Nov 04 2018 at 22:04):
@Rob Hausam, so you, perchance, have a cat? :)
Rob Hausam (Nov 04 2018 at 22:37):
Well, as a matter of fact, there was a cat sitting on my computer for a few minutes a bit earlier this afternoon, but it's my daughter's, not mine. And I had no idea that she has an interest in logical modeling. :)
David Hay (Nov 04 2018 at 23:27):
logical models are everywhere!
Lloyd McKenzie (Nov 04 2018 at 23:46):
Maybe that's what they're doing when they get hold of a ball of yarn?
Brian Postlethwaite (Nov 05 2018 at 01:26):
Do you know how long that yarn is? Sounds like a useful measure
David Hay (Nov 05 2018 at 02:01):
nothing like a good old yarn...
Last updated: Apr 12 2022 at 19:14 UTC
