kkuo

 @miller79 a diagram hopefully helps with illustration the problem a bit better.

Meeting 9/6 Decided to not add a status - Too late, spec is sort of locked down - Compliance is the same regardless of modification to the spec, so if...

### Webhook Scenarios - _When_ I have a fetch-available-appointments webhook event registered with the TMS, _then_ I should receive the results via the callBackURL that I have registered with the...

> > then I should receive a synchronous FAILURE code so that I am aware of the problem with the webhook and take appropriate actions > > or were you...

Adding comment from @GranataJBH >Following up on some of the actions from last week's meeting, my plan is to kick off a discussion in the beta GitHub with the below....

Summarizing some conversation over slack on why we can't realistically force TMSs to implement the request and response bodies faithfully and only consider those who did to be in compliance....

Action item: add language saying request body/response extensions by TMS are not guaranteed to be supported in future spec revisions.