Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CP: Dates for a health worker's posting should be captured #13

Open
litlfred opened this issue Mar 3, 2014 · 3 comments
Open

CP: Dates for a health worker's posting should be captured #13

litlfred opened this issue Mar 3, 2014 · 3 comments

Comments

@litlfred
Copy link
Contributor

litlfred commented Mar 3, 2014

There should be optional data elements to capture the expected start and end dates for a posting/associate of a health worker at a facility.

This particular use case came up in Ghana for community health workers -- as they are will be temporary contract employees, it would be good to be able to plan for turn-over.

More generally, this helps to answer the question of when there is the potential for a particular facility to provide a service. It is analogous to the operating hours of a facility.

Straw Man Proposal:

  1. Add a new complex data type:
<xs:complexType name="operatingDate">
    <xs:sequence>
      <xs:element name="beginEffectiveDate" type="xs:date"/>
      <xs:element name="endEffectiveDate" type="xs:date" minOccurs="0"/>
    </xs:sequence>
  </xs:complexType>
  1. Have the complex type operatingHours extend operatingDate

3)add an optional element operatingDate of type operatingDate under /providerDirectory/provider/facilities/facility

@sgrannis
Copy link

sgrannis commented Mar 3, 2014

From my perspective seems like a reasonable element to support. I assume the "minOccurs" parameter of "0" indicates the "endEffectiveDate" is optional? (my sense is "endEffectiveDate" should be optional)

@litlfred
Copy link
Contributor Author

litlfred commented Mar 5, 2014

Per discussion on the Provide Registry group:
https://groups.google.com/forum/#!topic/provider-registry/OcLge1k6dcQ
This solution is proposed:

  1. Modify the operatingHours data type so that dayOfTheWeek is minoccurs=0 and unbounded
  2. Allow an operatingHours element under /CSD/providerDirectory/provider/facilties/facility
  3. Declare more precisely how operatingHours should be interpreted.

For example when determining schedulable time for a health worker providing a service at a facility the following precedence rules apply:
-If any /CSD/providerDirectory/provider/facilties/facility/service/operatingHours exist, they take precedence over any of the other elements defined below. The other elements below are ignored.
-If any /CSD/providerDirectory/provider/facilties/facility/operatingHours exist, then they take
next precedence over any of the other elements defined below. The other elements below are ignored.
-If any /CSD/facilityDirectory/facility/operatingHours exists, then they are used for determine the schedulable time
-if none of the above elements exist, then it is assumed that there are no restrictions on schedulable time

@litlfred
Copy link
Contributor Author

Under consideration to add to CP #726 from Sylvie

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants