Do we need id properties on all the input Parameters resources?

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

Do we need id properties on all the input Parameters resources? #65

Closed cooperthompson closed 6 years ago

cooperthompson commented 6 years ago

All of the example request bodies (e.g. 2.3.3)have an id in the Parameters resource. Like "id": "pcp-hold".

Do we need ids here? I would think not.

Healthedata1 commented 6 years ago

dealers choice I think. I will remove.