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
Branch surgery model explanation #561
Labels
Appointments
Issue associated with Appointments Management capability
Lower priority
Can live without in this release
Milestone
Comments
jonnyry
added
the
Appointments
Issue associated with Appointments Management capability
label
Oct 11, 2018
jonnyry
pushed a commit
that referenced
this issue
Oct 13, 2018
jonnyry
pushed a commit
that referenced
this issue
Oct 13, 2018
jonnyry
pushed a commit
that referenced
this issue
Oct 13, 2018
jonnyry
pushed a commit
that referenced
this issue
Oct 13, 2018
jonnyry
pushed a commit
that referenced
this issue
Oct 13, 2018
jonnyry
pushed a commit
that referenced
this issue
Oct 13, 2018
jonnyry
pushed a commit
that referenced
this issue
Oct 14, 2018
jonnyry
pushed a commit
that referenced
this issue
Oct 15, 2018
jonnyry
pushed a commit
that referenced
this issue
Oct 15, 2018
jonnyry
pushed a commit
that referenced
this issue
Oct 15, 2018
jonnyry
pushed a commit
that referenced
this issue
Oct 15, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Appointments
Issue associated with Appointments Management capability
Lower priority
Can live without in this release
Though the specification does cover branch surgeries at points in the specification it is fragmented across several pages, and it would be useful to explicitly call out how the GP Connect model for branch surgeries works, and the relationship between elements.
Not strictly necessary but it given the changes in #560 and #559 it would be useful to improve this area at the same time.
The text was updated successfully, but these errors were encountered: