Skip to content
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

Create structured capability statement to allow for future separation of Appointments and Structured capabilities #668

Closed
jonnyry opened this issue Jul 4, 2019 · 1 comment
Assignees
Labels
Core Issue associated with the Core elements of the spec
Milestone

Comments

@jonnyry
Copy link
Member

jonnyry commented Jul 4, 2019

To do:

  • Create Structured capability statement endpoint within Structured capability
  • Make clear that Appointments and Structured APIs are independent of each other, and [in the future] could resolve to different URL paths on the same system
@jonnyry jonnyry added this to the 1.2.4 milestone Jul 4, 2019
@jonnyry jonnyry self-assigned this Jul 4, 2019
@jonnyry jonnyry added the Core Issue associated with the Core elements of the spec label Aug 2, 2019
@jonnyry jonnyry modified the milestones: 1.2.4, 1.2.x (Futures 1) Aug 2, 2019
jonnyry pushed a commit that referenced this issue Oct 1, 2019
jonnyry pushed a commit that referenced this issue Oct 1, 2019
jonnyry pushed a commit that referenced this issue Oct 1, 2019
jonnyry pushed a commit that referenced this issue Oct 1, 2019
@jonnyry jonnyry changed the title Changes to support multiple providers at a single organisation Create structured capability statement to allow for future seperation of Appointments and Structured Oct 23, 2019
@jonnyry jonnyry changed the title Create structured capability statement to allow for future seperation of Appointments and Structured Create structured capability statement to allow for future separation of Appointments and Structured capabilities Oct 23, 2019
@jonnyry
Copy link
Member Author

jonnyry commented Oct 23, 2019

IGNORE ASSOCIATED COMMITS ABOVE THIS POINT - they were made prior to a change in direction and are in a now defunct branch.

jonnyry pushed a commit that referenced this issue Nov 6, 2019
… of Appointments and Structured capabilities #668
@jonnyry jonnyry closed this as completed Nov 6, 2019
jonnyry pushed a commit that referenced this issue Nov 6, 2019
… of Appointments and Structured capabilities #668
jonnyry pushed a commit that referenced this issue Nov 6, 2019
… of Appointments and Structured capabilities #668
jonnyry pushed a commit that referenced this issue Nov 7, 2019
… of Appointments and Structured capabilities #668
jonnyry pushed a commit that referenced this issue Nov 7, 2019
… of Appointments and Structured capabilities #668
jonnyry pushed a commit that referenced this issue Nov 7, 2019
… of Appointments and Structured capabilities #668
jonnyry pushed a commit that referenced this issue Feb 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Core Issue associated with the Core elements of the spec
Projects
None yet
Development

No branches or pull requests

1 participant