Stream: implementers
Topic: Personnel Management with FHIR?
Andy Kendall (Jan 05 2017 at 17:05):
Hi, We have implemented an internet facing PHR secured with OAuth2. Now a question has been asked as to whether the infrastructure can be reused for some self service personnel use cases, the first being online access to payslips for health service staff.
I have no doubt this *can* be done, but would welcome opinions on whether this *should* be done, or if it is outside the intended scope of FHIR. I notice that HL7 had a Personnel Management working group which is now merged into Patient Administration.
In the first instance we would store payslips (thinking PaymentNotice as a candidate resource type, possibly extended to link to a pdf payslip). Another potential use case is shift selection for bank nurses - Schedule and Slot are possibilities I've identified as candidates.
Any thoughts/opinions appreciated.
Lloyd McKenzie (Jan 05 2017 at 19:41):
@Andy Kendall At present, there are no resources to represent HR concepts like payroll. Our general leaning would be to avoid including that in FHIR as it's not terribly healthcare-specific. However, we'd be guided by the will of the implementer community. I.e. If lots of independent implementers indicate they want support for (some) payroll concepts in FHIR, then we'd look at doing that. Unless/until that happens, you'd need to look at the Basic resource.
Andy Kendall (Jan 06 2017 at 10:07):
Thanks @Lloyd McKenzie, that's really helpful. The Basic resource along with DocumentReference would cover our immediate requirement nicely I think. From what you say, it is doubtful that HR concepts will be included in FHIR - but in our context I suspect that consumers/developers of the HR API will be the same teams who consume the PHR and other FHIR based interfaces and therefore already have the FHIR tooling and skills. This I think is another compelling reason (along with re-use) for us considering FHIR in this context.
However, payslips are a simple use case - more tricky is the representation of shifts which need to be filled (think self service shift request by ward nurses). My first thought was that Slot and Schedule showed lots of synergies and could be profiled to meet the need - but perhaps that is a step too far - after all to use Basic for this would result in a quite complicated resource which would probably in the end look very like Slot/Schedule and starts to feel more like a reason why FHIR isn't a good choice here. Would you agree with that?
The general driver here is the push to provide internet access for both Patients and professionals to relevant data held in on-premise systems.
Brian Postlethwaite (Jan 06 2017 at 11:47):
We are modelling our internal system with shifts as slots as you've described in a Community based scheduling application.
Brian Postlethwaite (Jan 06 2017 at 11:48):
And our staff will be paid based on shifts (slots), not appointments, but that's not always the case for us also.
Lloyd McKenzie (Jan 06 2017 at 20:26):
I think Slot and Schedule *should* meet your need for managing shifts. That's certainly part of their intended scope.
Last updated: Apr 12 2022 at 19:14 UTC
