Stream: implementers
Topic: New page for spec?
Grahame Grieve (Dec 09 2019 at 22:43):
I can add a new page to the spec that is just all the UML diagrams in a single page. is this a good idea?
Richard Townley-O'Neill (Dec 10 2019 at 03:13):
I don't think I'd use it.
Vadim Peretokin (Dec 10 2019 at 10:03):
I don't see myself using it as well, If it's not too much of a maintenance burden, I think it'll be a good idea to try! It could help show up in searches for images about FHIR and perhaps it'll be useful as an introduction for FHIR beginners.
René Spronk (Dec 10 2019 at 10:17):
In educational settings it's unlikely that you'd swamp an attendee with tons of uml diagrams. Just one or two will suffice, they'll get the idea.
Lloyd McKenzie (Dec 10 2019 at 13:09):
It's unlikely to satisfy the crowd who wants a single integrated UML diagram. I can't think of anyone else who would want 'all' of them.
Richard Townley-O'Neill (Dec 12 2019 at 04:45):
It might be good for showing the problems with using UML class diagrams for such a highly connected model. :grinning_face_with_smiling_eyes:
nicola (RIO/SS) (Dec 12 2019 at 08:34):
I like this idea! Probably some details can be skipped. Show only summary elements for example! And it can be interactive like http://visualdataweb.de/webvowl/#
Grahame Grieve (Dec 12 2019 at 10:21):
well, if someone wanted to do the work for a page like that, we could probably add it.
nicola (RIO/SS) (Dec 12 2019 at 10:33):
https://healthsamurai.github.io/visual-fhir/
Grahame Grieve (Dec 12 2019 at 10:36):
I'm not sure what I'm looking at there, or whether people would find something like this useful.
nicola (RIO/SS) (Dec 12 2019 at 10:42):
I will try to make this somehow useful :) Such visualizations can be useful to see FHIR from bird's-eyes. For refs, there is a better diagram https://observablehq.com/@d3/hierarchical-edge-bundling
Grahame Grieve (Dec 12 2019 at 10:45):
personally, I found representations like this more curio than genuinely useful. So I'm not going to invest more than a few hours into it.... but I'm open to be swaying by other people's opinions.
René Spronk (Dec 12 2019 at 12:42):
For Grapdef (with directed edges) they could be useful as a documentation tool. For anything which has too many nodes it probably only adds to the confusion.
nicola (RIO/SS) (Dec 12 2019 at 12:46):
Make good visualization of a complicated structure is hard, but not "impossible" - I will spend a couple more hours when I will have some free time.
Lloyd McKenzie (Dec 12 2019 at 12:49):
You'd have to exclude extensions and modifierExtensions - as they allow everything to connect with everything...
nicola (RIO/SS) (Dec 12 2019 at 13:12):
I used only basic reference elements.
nicola (RIO/SS) (Dec 13 2019 at 10:06):
Iteration #2 - dark theme + clickable - https://healthsamurai.github.io/visual-fhir/
Lloyd McKenzie (Dec 13 2019 at 12:29):
What am I supposed to infer from this diagram? Lots of things relate to Patient & Practitioner?
nicola (RIO/SS) (Dec 13 2019 at 13:16):
This is mostly Xmas toy, but @Lloyd McKenzie you can see on qualitative level how FHIR resources are linked/coupled :) For example you can see how painful will be to remove PractitionerRole and some strange not-linked resources.
John Silva (Dec 13 2019 at 13:34):
A few years ago one of the guys I worked with showed this kind of graphic display for navigation. I think there can be a benefit to it, I just don't remember how/why. I think the example was doing a Google Search and then the results come back in this kind of 'association bubble' that gives you an idea what might have the most relevance. (I think of 'word bubbles' -- they convey info just by the size of the words)
Last updated: Apr 12 2022 at 19:14 UTC
