search

argonautproject / scheduling

Argonaut Scheduling and Appointments: This project supports basic patient and provider access to a provider's calendar and appointment requests, including APIs and guidance for searching and publishing a providers schedule andrequesting, cancelling or updating an appointment.
http://www.fhir.org/guides/argonaut/scheduling/
15 stars 2 forks source link

Issues with Coverage Resource #46

Closed Healthedata1 closed 6 years ago

Healthedata1 commented 6 years ago

(Note much of this is not related to the Scheduling IG but to the Coverage resource itself.)

  1. subscriber is not always a registered patient, which leaves us with these options:
    • contained patient resource
    • bundle with patient somehow
  2. identifier vs subscriberId may often be the same.
    • no identifier.type value for this
    • subscriberId is type string - why not type Identifier?
  3. grouping structure is just weird
    • A better structure?:
      • Plan 0..*
      • Type 1..1 type codeableConcept ( valueset of 'plan', 'group', 'subplan', 'subgroup', etc. and allows for display)
      • identifier 1..1 type Identifier
cooperthompson commented 6 years ago

I agree - Coverage needs some modeling love. PA and FM have had several discussions around subscriber IDs and identifiers and grouping... I don't think we want to try to solve that can of worms here.

I think for our purposes (US-realm), we can probably get by with what is in the resource right now (for grouping and subscriber IDs. For non-patient subscribers, we'd probably want a contained RelatedPerson, not Patient.

Healthedata1 commented 6 years ago

OK will close as out of scope.