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

ITI-65: Allow Folder Lists to have PUT request #55

Closed
jlamy opened this issue Apr 29, 2021 · 3 comments
Closed

ITI-65: Allow Folder Lists to have PUT request #55

jlamy opened this issue Apr 29, 2021 · 3 comments
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@jlamy
Copy link
Contributor

jlamy commented Apr 29, 2021

Section Number 11.4.1.2.1

Issue ITI-65 constrains each bundle entry request to POST. This would mean if an MHD Document Source wanted to add Document References to an existing Folder, it would have to do it outside an ITI-65, e.g. in a single PUT.

Proposed Change Because ITI-65 adds valuable context and provenance, we should allow Folder Lists to use the PUT request in ITI-65. Additionally, we should consider guidance that ITI-65 should be the only mechanism used to update Folder Lists. We enforce this in the eHealth Exchange, but it is a cross-community environment. It may be the case that inside a community, systems may want to allow more flexibility.

Priority: Medium

@JohnMoehrke
Copy link
Contributor

agreed on PUT, this was an oversite.

Comments regarding not allowing any creates/updates/deletes/queries outside of the approved MHD methods is unusual for a profile to do. Anything done outside of the profiled interactions are simply outside the profile control. Anything done outside the profiled interactions might work, but the profile can't claim anything about that. It might work, it might not. What is the harm overall if it works or is failed?

@jlamy
Copy link
Contributor Author

jlamy commented May 4, 2021

Ok, thanks. That works for me. No need to sharply constrain at this level, but how about at least suggest that it would be the preferred way to update Folder?

@JohnMoehrke
Copy link
Contributor

it is the profiled way to update a Folder. All others are not part of the profiled behavior.

@JohnMoehrke JohnMoehrke self-assigned this May 5, 2021
@JohnMoehrke JohnMoehrke added the enhancement New feature or request label May 5, 2021
@JohnMoehrke JohnMoehrke added this to the 4.0.0 milestone May 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants