search

smart-on-fhir / smart-scheduling-links

Clinical Appointment Slot Discovery
28 stars 15 forks source link

Consider loosening the VTrckS PIN identifier requirement #7

Closed cooperthompson closed 3 years ago

cooperthompson commented 3 years ago

Right now, it seems like if you send a Location identifier, it has to be the VTrckS PIN. I'm not sure if that is the intent or not, but could we allow for sending identifiers that are not VTrckS PINs?

I don't know for sure, but I'm suspicious we'll see other systems want to use this spec beyond just USDS, so our implementation intends to be a little flexible regarding what identifiers are included.

jmandel commented 3 years ago

The intention is: if you have a VTrcks PIN, Location.identifier is where it goes.

Agreed that the current language is overly specific (i.e., doesn't explain that you can use other Identifiers too). I was kind of waiting until someone had another use case to avoid making the docs more confusing, but since you've now raised it... I'll propose a tweak.

jmandel commented 3 years ago

Would appreciate a quick look at #8 @cooperthompson .