Dates of a health worker's posting

Hi All,
Based on requirements for a health worker registry in Ghana, I have opened an issue:
  https://github.com/openhie/openinfoman/issues/13
for discussion as a potential Change Proposal. I would appreciate your feedback.

The main point is that there is no place to track the begin dates of a health worker’s posting at a facility.

Having that information in CSD (and it is quite common to have the beginning date of a posting) would allow one to better the question on which services are provided at a facility within a given date.

Cheers,
-carl

Hi Carl.

So… I’m going to make some assumptions based on the
existing CSD schema:

#1. The health worker’s relationship to the facility is
specified through the provider-facility relationship (CSD doc page 86). Quote:
A provider may have a relationship with multiple facilities from which care
services are provided; these are cross-referenced here by facility ID. ./facilities/facility/@oid

#2. The health worker’s relationship to the services
provided at the facility are specified through the provider-facility-service
relationship (CSD doc page 86) . Quote:
A provider may have service-delivery relationships with a facility or
facilities. A reference to each Service + Facility combination is maintained;
this supports discovery regarding where (and when) this provider is delivering
which services. ./facilities/facility/service[@oid]

If we follow assumptions 1 & 2, and the health worker
is deemed to provide even a generic service at the indicated facility, then the
attributes of the “service” data type are available to be leveraged.
This includes “operating hours”, which has the following schema:

xs:sequence

<xs:element
name=“openFlag” type=“xs:boolean”/>

<xs:element

name=“dayOfTheWeek” type=“xs:integer”/>

<xs:element

name=“beginningHour” type=“xs:time”
minOccurs=“0”/>

<xs:element

name=“endingHour” type=“xs:time”
minOccurs=“0”/>

<xs:element

name=“beginEffectiveDate” type=“xs:date”/>

<xs:element

name=“endEffectiveDate” type=“xs:date” minOccurs=“0”/>

</xs:sequence> </xs:complexType>

It would appear that, to use the operatingHours
construct, we would need to indicate which days of the week the HW is providing
this service at this facility; there is not a way to just say “all of
them”. There is a way, however, to put the begin and end effective dates
on this.

I’m not convinced that the right answer here is to put in
a new construct that could potentially be in conflict with this one. Do we have
an “eat our own cooking” option, here? If we do need a change, should
it be to make dayOfTheWeek an optional data element in the same way that the
“time” elements are optional?

What do others think about this idea?

Warmest regards,

Derek.

···

On Monday, March 3, 2014 5:39:18 AM UTC-5, cleitner wrote:

Hi All,

Based on requirements for a health worker registry in Ghana, I have opened an issue:

    [https://github.com/openhie/openinfoman/issues/13](https://github.com/openhie/openinfoman/issues/13)

for discussion as a potential Change Proposal. I would appreciate your feedback.

The main point is that there is no place to track the begin dates of a health worker’s posting at a facility.

Having that information in CSD (and it is quite common to have the beginning date of a posting) would allow one to better the question on which services are provided at a facility within a given date.

Cheers,

-carl

HI Derek,
I am not sure we want to use the operatingHours of the service, it may end of being a lot of maintenance if we have more than one service offered by a provider at a facility. This was the main reason for suggesting to add something under provider/facilities/facility
that would be a “default” for all the services listed underneath.

The dayOfTheWeek thing was the main reason that I suggested the new complex type. I suppose that making the dayOfTheWeek a minOccurs=0 and unbounded would solve the problem. It puts a bit more logic on the free/busy processor but keeps the data model
cleaner.

Cheers,

-carl

···

On Mar 3, 2014, at 3:25 PM, Derek Ritz derek.ritz@gmail.com wrote:

Hi Carl.

So… I’m going to make some assumptions based on the existing CSD schema:

#1. The health worker’s relationship to the facility is specified through the provider-facility relationship (CSD doc page 86). Quote: A provider may have a relationship with multiple facilities from which care services are provided;
these are cross-referenced here by facility ID.
./facilities/facility/@oid

#2. The health worker’s relationship to the services provided at the facility are specified through the provider-facility-service relationship (CSD doc page 86) .
Quote: A provider may have service-delivery relationships with a facility or facilities. A reference to each Service + Facility combination is maintained; this supports discovery regarding where (and when) this provider is delivering which services.
./facilities/facility/service[@oid]

If we follow assumptions 1 & 2, and the health worker is deemed to provide even a generic service at the indicated facility, then the attributes of the “service” data type are available to be leveraged. This includes “operating hours”,
which has the following schema:

<xs:element name=“openFlag” type=“xs:boolean”/>

<xs:element name="dayOfTheWeek" type="xs:integer"/>
<xs:element name="beginningHour" type="xs:time" minOccurs="0"/>
<xs:element name="endingHour" type="xs:time" minOccurs="0"/>
<xs:element name="beginEffectiveDate" type="xs:date"/>
<xs:element name="endEffectiveDate" type="xs:date" minOccurs="0"/>

</xs:sequence> </xs:complexType>

It would appear that, to use the operatingHours construct, we would need to indicate which days of the week the HW is providing this service at this facility; there is not a way to just say “all of them”. There is a way, however, to
put the begin and end effective dates on this.

I’m not convinced that the right answer here is to put in a new construct that could potentially be in conflict with this one. Do we have an “eat our own cooking” option, here? If we do need a change, should it be to make dayOfTheWeek
an optional data element in the same way that the “time” elements are optional?

What do others think about this idea?

Warmest regards,

Derek.

On Monday, March 3, 2014 5:39:18 AM UTC-5, cleitner wrote:

Hi All,

Based on requirements for a health worker registry in Ghana, I have opened an issue:

    [https://github.com/openhie/openinfoman/issues/13](https://github.com/openhie/openinfoman/issues/13)

for discussion as a potential Change Proposal. I would appreciate your feedback.

The main point is that there is no place to track the begin dates of a health worker’s posting at a facility.

Having that information in CSD (and it is quite common to have the beginning date of a posting) would allow one to better the question on which services are provided at a facility within a given date.

Cheers,

-carl

You received this message because you are subscribed to the Google Groups “OpenHIE Health Worker Registry” group.

To unsubscribe from this group and stop receiving emails from it, send an email to
provider-registry+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

Hi Carl (and everyone).

Personally, I like the idea of keeping the data model cleaner. Do you see
(or does anyone else see) any problems with setting minOccurs=0 for the
dayOfTheWeek attribute (see the thread - 2 messages down)? We would have to
ensure that any CP (for IHE) indicated what the default processing would
have to be for a FreeBusy service call if days of the week are unspecified.

It looks like a viable option with that relaxation.

Thoughts?

Derek.

PS: I'm noticing that there are behaviours, for attributes like
operatingHours, that we should likely specify in the CSD profile to ensure
that they are used the same way by everyone. My sense, now that we're into
using it, is that there are a few attributes where the behaviour is not
obvious. Is anyone else feeling that way?

*Derek Ritz, *P.Eng., CPHIMS-CA

*ecGroup Inc.*

+1 (905) 515-0045

www.ecgroupinc.com

This communication is intended only for the party to whom it is addressed,
and may contain information which is privileged or confidential. Any other
delivery, distribution, copying or disclosure is strictly prohibited and is
not a waiver of privilege or confidentiality. If you have received this
telecommunication in error, please notify the sender immediately by return
electronic mail and destroy the message and any attachments.

--------------------------------------------------------------------------------
Le présent courriel et les documents qui y sont joints sont confidentiels
et protégés et s'adressent exclusivement au destinataire mentionné
ci-dessus. L'expéditeur ne renonce pas aux droits et privilèges qui s'y
rapportent ni à leur caractère confidentiel. Toute prise de connaissance,
diffusion, utilisation ou reproduction de ce message ou des documents qui y
sont joints, ainsi que des renseignements que chacun contient, par une
personne autre que le destinataire prévu est interdite. Si vous recevez ce
courriel par erreur, veuillez le détruire immédiatement et m'en informer.

*From:* ihe-csd-implementors@googlegroups.com [mailto:
ihe-csd-implementors@googlegroups.com] *On Behalf Of *Carl Leitner
*Sent:* Monday, March 3, 2014 1:00 PM
*To:* Derek Ritz
*Cc:* Provider Registry Google Group;
ihe-csd-implementors@googlegroups.com
*Subject:* Re: Dates of a health worker's posting

HI Derek,

I am not sure we want to use the operatingHours of the service, it may
end of being a lot of maintenance if we have more than one service offered
by a provider at a facility. This was the main reason for suggesting to
add something under provider/facilities/facility that would be a "default"
for all the services listed underneath.

The dayOfTheWeek thing was the main reason that I suggested the new
complex type. I suppose that making the dayOfTheWeek a minOccurs=0 and
unbounded would solve the problem. It puts a bit more logic on the
free/busy processor but keeps the data model cleaner.

Cheers,
-carl

Hi Carl.

So... I'm going to make some assumptions based on the existing CSD schema:

#1. The health worker's relationship to the facility is specified through
the provider-facility relationship (CSD doc page 86). Quote: A provider may
have a relationship with multiple facilities from which care services are
provided; these are cross-referenced here by facility ID.
./facilities/facility/@oid

#2. The health worker's relationship to the services provided at the
facility are specified through the provider-facility-service relationship
(CSD doc page 86) . Quote: A provider may have service-delivery
relationships with a facility or facilities. A reference to each Service +
Facility combination is maintained; this supports discovery regarding where
(and when) this provider is delivering which services.
./facilities/facility/service[@oid]

If we follow assumptions 1 & 2, and the health worker is deemed to
provide even a generic service at the indicated facility, then the
attributes of the "service" data type are available to be leveraged. This
includes "operating hours", which has the following schema:

<!--informed by HL7-OMG HSD spec; Sunday=0, Monday=1...)-->
<xs:complexType name="operatingHours"> <xs:sequence>

    <xs:element name="openFlag" type="xs:boolean"/>

    <xs:element name="dayOfTheWeek" type="xs:integer"/>

    <xs:element name="beginningHour" type="xs:time" minOccurs="0"/>

    <xs:element name="endingHour" type="xs:time" minOccurs="0"/>

    <xs:element name="beginEffectiveDate" type="xs:date"/>

    <xs:element name="endEffectiveDate" type="xs:date" minOccurs="0"/>

</xs:sequence> </xs:complexType>

It would appear that, to use the operatingHours construct, we would need
to indicate which days of the week the HW is providing this service at this
facility; there is not a way to just say "all of them". There is a way,
however, to put the begin and end effective dates on this.

I'm not convinced that the right answer here is to put in a new construct
that could potentially be in conflict with this one. Do we have an "eat our
own cooking" option, here? If we do need a change, should it be to make
dayOfTheWeek an optional data element in the same way that the "time"
elements are optional?

What do others think about this idea?

Warmest regards,

Derek.

Hi All,
Based on requirements for a health worker registry in Ghana, I have opened
an issue:
        https://github.com/openhie/openinfoman/issues/13
for discussion as a potential Change Proposal. I would appreciate your
feedback.

The main point is that there is no place to track the begin dates of a
health worker's posting at a facility.

Having that information in CSD (and it is quite common to have the
beginning date of a posting) would allow one to better the question on
which services are provided at a facility within a given date.

Cheers,
-carl

--
You received this message because you are subscribed to the Google Groups
"OpenHIE Health Worker Registry" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to provider-registry+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups
"ihe-csd-implementors" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to ihe-csd-implementors+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

···

On Mar 3, 2014, at 3:25 PM, Derek Ritz <derek.ritz@gmail.com> wrote:
On Monday, March 3, 2014 5:39:18 AM UTC-5, cleitner wrote:

--
Derek Ritz
----------------
This email may contain confidential information intended only for the
recipient. If you receive it by accident, please delete it.

Hi Carl (and everyone).

Personally, I like the idea of keeping the data model cleaner. Do you see (or does anyone else see) any problems with setting minOccurs=0 for the dayOfTheWeek
attribute (see the thread – 2 messages down)? We would have to ensure that any CP (for IHE) indicated what the default processing would have to be for a FreeBusy service call if days of the week are unspecified.

It looks like a viable option with that relaxation.

Thoughts?

Derek.

PS: I’m noticing that there are behaviours, for attributes like operatingHours, that we should likely specify in the CSD profile to ensure that they are used
the same way by everyone. My sense, now that we’re into using it, is that there are a few attributes where the behaviour is not obvious. Is anyone else feeling that way?

···

**Derek Ritz,**P.Eng., CPHIMS-CA

ecGroup Inc.

+1 (905) 515-0045

www.ecgroupinc.com

This communication is intended only for the party to whom it is addressed, and may contain information which is privileged or confidential. Any other delivery,
distribution, copying or disclosure is strictly prohibited and is not a waiver of privilege or confidentiality. If you have received this telecommunication in error, please notify the sender immediately by return electronic mail and destroy the message and
any attachments.


Le présent courriel et les documents qui y sont joints sont confidentiels et protégés et s’adressent exclusivement au destinataire mentionné ci-dessus. L’expéditeur
ne renonce pas aux droits et privilèges qui s’y rapportent ni à leur caractère confidentiel. Toute prise de connaissance, diffusion, utilisation ou reproduction de ce message ou des documents qui y sont joints, ainsi que des renseignements que chacun contient,
par une personne autre que le destinataire prévu est interdite. Si vous recevez ce courriel par erreur, veuillez le détruire immédiatement et m’en informer.

From:
ihe-csd-implementors@googlegroups.com [mailto:ihe-csd-implementors@googlegroups.com]
On Behalf Of Carl Leitner
Sent: Monday, March 3, 2014 1:00 PM
To: Derek Ritz
Cc: Provider Registry Google Group;
ihe-csd-implementors@googlegroups.com
Subject: Re: Dates of a health worker’s posting

HI Derek,

I am not sure we want to use the operatingHours of the service, it may end of being a lot of maintenance if we have more than one service offered by a provider at a facility. This was the main reason for suggesting to add something under
provider/facilities/facility that would be a “default” for all the services listed underneath.

The dayOfTheWeek thing was the main reason that I suggested the new complex type. I suppose that making the dayOfTheWeek a minOccurs=0 and unbounded would solve the problem. It puts a bit more logic on the free/busy processor but keeps
the data model cleaner.

Cheers,
-carl

On Mar 3, 2014, at 3:25 PM, Derek Ritz derek.ritz@gmail.com wrote:

Hi Carl.

So… I’m going to make some assumptions based on the existing CSD schema:

#1. The health worker’s relationship to the facility is specified through the provider-facility relationship (CSD doc page 86). Quote: A provider may have a relationship with multiple facilities from which care services are provided;
these are cross-referenced here by facility ID.
./facilities/facility/@oid

#2. The health worker’s relationship to the services provided at the facility are specified through the provider-facility-service relationship (CSD doc page 86) . Quote: A provider may have service-delivery relationships with a facility
or facilities. A reference to each Service + Facility combination is maintained; this supports discovery regarding where (and when) this provider is delivering which services. ./facilities/facility/service[@oid]

If we follow assumptions 1 & 2, and the health worker is deemed to provide even a generic service at the indicated facility, then the attributes of the “service” data type are available to be leveraged. This includes “operating hours”,
which has the following schema:

<xs:element name=“openFlag” type=“xs:boolean”/>

<xs:element name=“dayOfTheWeek” type=“xs:integer”/>

<xs:element name=“beginningHour” type=“xs:time” minOccurs=“0”/>

<xs:element name=“endingHour” type=“xs:time” minOccurs=“0”/>

<xs:element name=“beginEffectiveDate” type=“xs:date”/>

<xs:element name=“endEffectiveDate” type=“xs:date” minOccurs=“0”/>

</xs:sequence> </xs:complexType>

It would appear that, to use the operatingHours construct, we would need to indicate which days of the week the HW is providing this service at this facility; there is not a way to just say “all of them”. There is a way, however, to
put the begin and end effective dates on this.

I’m not convinced that the right answer here is to put in a new construct that could potentially be in conflict with this one. Do we have an “eat our own cooking” option, here? If we do need a change, should it be to make dayOfTheWeek
an optional data element in the same way that the “time” elements are optional?

What do others think about this idea?

Warmest regards,

Derek.

On Monday, March 3, 2014 5:39:18 AM UTC-5, cleitner wrote:

Hi All,
Based on requirements for a health worker registry in Ghana, I have opened an issue:

    [https://github.com/openhie/openinfoman/issues/13](https://github.com/openhie/openinfoman/issues/13)

for discussion as a potential Change Proposal. I would appreciate your feedback.

The main point is that there is no place to track the begin dates of a health worker’s posting at a facility.

Having that information in CSD (and it is quite common to have the beginning date of a posting) would allow one to better the question on which services are provided at a facility within a given date.

Cheers,
-carl


You received this message because you are subscribed to the Google Groups “OpenHIE Health Worker Registry” group.
To unsubscribe from this group and stop receiving emails from it, send an email to
provider-registry+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


You received this message because you are subscribed to the Google Groups “ihe-csd-implementors” group.
To unsubscribe from this group and stop receiving emails from it, send an email to
ihe-csd-implementors+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.