Stream: implementers
Topic: New resource list
Grahame Grieve (Feb 27 2017 at 04:51):
There's a new layout at http://build.fhir.org/resourcelist.html
Grahame Grieve (Feb 27 2017 at 04:51):
it's driven by a more architectural approach. It's more systematic, but less... conven ient
Grahame Grieve (Feb 27 2017 at 04:51):
comments welcome
Lloyd McKenzie (Feb 27 2017 at 05:02):
Would be good to make the far-left labels vertical to waste less space. Conformance should be listed before security. Don't like the "Summary" and "Diagnosis" labels. I thought the proposal had labled them something else?
Grahame Grieve (Feb 27 2017 at 05:48):
summary was labelled 'clinical' but that was silly sitting next to 'clinical resources'
Grahame Grieve (Feb 27 2017 at 05:48):
diagnosis is my typo
Lloyd McKenzie (Feb 27 2017 at 06:13):
But they're not all summary resources - some of them are detail resources.
Muhammad Abubakar Ikram (Feb 27 2017 at 06:29):
Sir please large the font of tooltip over resource names.
Grahame Grieve (Feb 27 2017 at 06:30):
I don't think we have any control over that
Grahame Grieve (Feb 27 2017 at 06:31):
I don't mind if you have something other than 'summary' but it can't be 'clinical
Lloyd McKenzie (Feb 27 2017 at 06:31):
It should be a style setting somewhere or other. Anyone with expertise is welcome to chime in.
Muhammad Abubakar Ikram (Feb 27 2017 at 06:32):
I hope I can do that
Grahame Grieve (Feb 27 2017 at 06:33):
http://stackoverflow.com/questions/15027301/change-font-size-of-td-title-attribute - bit of mucking around
Grahame Grieve (Feb 27 2017 at 06:33):
I think it shoud be a browser thing - hint size is a local thing not a server thing
Muhammad Abubakar Ikram (Feb 27 2017 at 06:45):
Yes I think you are right. but there are some jquery libs that can do the job.
Grahame Grieve (Feb 27 2017 at 06:46):
need to be very careful about jquery - we already use it, but sparingly. Need to be the same version for all uses, needs to work offline, needs to be same across all browsers
Muhammad Abubakar Ikram (Feb 27 2017 at 06:47):
sir like this https://jqueryui.com/tooltip/
this is official one
Eric Haas (Feb 27 2017 at 07:01):
Media is missing and i don't like it Sticking stuff at top that nobody (well me) never uses or cares about. I think should be a popularity contest most used stuff at top. forgotten stuff at bottom
Eric Haas (Feb 27 2017 at 07:02):
maybe a third pragmatic view
view
John Moehrke (Feb 27 2017 at 14:42):
This resourcelist does not render well on mobile display. It is usable, as I can scroll right...
John Moehrke (Feb 27 2017 at 14:44):
although I focus more on foundation, I would think our audience would rather see base first, then foundation.
Eric Haas (Feb 27 2017 at 15:00):
Lemme clarify my response. I use this page for navigating to resources, so from that perspective I think this view a step backwards. But after further review of the content and its context it is very useful. I would however still like a view for navigating to the resources.
Grahame Grieve (Feb 27 2017 at 20:03):
well, we could have 3 views. Still seeing opinions on this
Brian Postlethwaite (Feb 27 2017 at 23:09):
Also, the veritcal text doesn't render in IE properly.
Muhammad Abubakar Ikram (Feb 28 2017 at 06:27):
As described Person resource is referring to a person that is outside the healthcare setting.
what comes in my mind that the Person resource is for the persons in the organization like CEO, Head of Department or HR admin.
*1st. So, in this case, we must have a PersonRole resource for that person in the organization. Like we have PractionerRole for the Practitioner
If the point 1st does not look appropriate then the 2nd point should be consider
*2nd. Group resource should also refer to the person resource so that we can say this person is lying in a specific group
I think by using one of the above techniques we will be able to define a person in an organization that is outside the healthcare setting in a more appropriate way.
Lloyd McKenzie (Feb 28 2017 at 16:02):
The Person definition needs work. Person is a "linking" resource - that should be first and foremost in the definition. Person has no role and can have no role associated with them. The "role" of Person is conveyed by the Patient, Practitioner or RelatedPerson resources.
Brian Postlethwaite (Feb 28 2017 at 23:10):
Yes as Lloyd describes it can be a linking resource, and also a registry that is for use outside the healthcare setting. So maintaining an overall list of people that haven't entered the healthcare system yet (e.g. In a local council could be rate payers - who could be eligible for receiving community services, or in an insurance system the subscribers - until they actually need to receive care).
Then once the enter into use in the healthcare system they will be entered as either Patient, RelatedPersion or Practitioner resources (depending what they are doing).
From your example of a CEO, that would be a practitioner (with a role of CEO) if you were actually recording that in the healthcare solution.
Person records don't perform anything, and can't have anything done to them, you need one of the other resources listed here to do that. (hence isn't a part of groups or anywhere else)
Lloyd McKenzie (Feb 28 2017 at 23:28):
Hi Brian,
I don't think your nuance of "outside of the healthcare system" is useful. Persons can't be referenced by any resource - which means they can't be used in any context inside our outside of the healthcare system except for linking. Someone who's eligible for a service is a Patient - they're in the role of actual or potential recipient of care.
Brian Postlethwaite (Feb 28 2017 at 23:32):
Outside the direct linkage usage I'd mostly I'd expect to see this interface on non healthcare systems to provide a list of potential people to use inside the healthcare system.
Brian Postlethwaite (Feb 28 2017 at 23:33):
Just as with my example of subscribers, members, or other person registries.
Muhammad Abubakar Ikram (Mar 01 2017 at 03:19):
Oh I see, @Brian Postlethwaite So, If I need more roles in PractionerRole I will add extensions/dataTypes in PractionerRole by creating a profile according to my neads?
Brian Postlethwaite (Mar 01 2017 at 03:19):
Just more PractitionerRole instances with the details of the new roles that the prac does.
Lloyd McKenzie (Mar 01 2017 at 03:34):
Subscribers are considered Patients when referenced by Coverage. I'd expect the registries of them to be the same. I don't think there's any circumstance where Person should be used except as a Linkage resource. (That was the agreement when FMG approved it . . .)
Brian Postlethwaite (Mar 01 2017 at 03:34):
Yes, by that time the are patients.
Lloyd McKenzie (Mar 01 2017 at 03:42):
Not sure what you mean "by that time". If you're a subscriber, your a Patient whether you're in a registry or attached to a Coverage. Person is role-less. I can't see how it could possibly be used for anything other than linking. And the agreement was that it wouldn't be. So not sure why the definition doesn't just say that explicitly.
Last updated: Apr 12 2022 at 19:14 UTC
