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

Servers Generally Don't Know What the Client Has Access To #53

Closed
slagesse-epic opened this issue Apr 1, 2022 · 0 comments · Fixed by #119
Closed

Servers Generally Don't Know What the Client Has Access To #53

slagesse-epic opened this issue Apr 1, 2022 · 0 comments · Fixed by #119
Assignees

Comments

@slagesse-epic
Copy link
Member

Section Number Identify the most specific section number the issue occurs (e.g. 4.1.2)

2:3.90.4.2.2

Issue Describe your issue. Don't write a book, but do include enough to indicate what you see as a problem.

The following text:

"All References (reference.reference element) to Resources defined in this transaction shall be populated with an accessible URL (see https://www.hl7.org/fhir/references-definitions.html#Reference.reference), unless the referenced resource is not present on a server accessible to the client."

is problematic because a server does not necessarily know what servers the client has access to.

Proposed Change Propose a resolution to your issue (e.g., suggested new wording or description of a way to address the issue). The committee might simply accept your suggested text. Even if they don't, it gives a good sense of what you are looking for. Leaving this blank means you can't imagine how to resolve the issue, which makes it easier for the committee to admit they can't imagine how to resolve it either and leave it unresolved.

Change to "...unless the referenced resource is not available at a URL known to the server"

Priority:

  • Low: Typo or other minor classification that an editor can manage. Requires no group discussion.
lukeaduncan added a commit that referenced this issue Jun 13, 2022
Removed reference to what a client is aware of from 3.90.4.2.2.  Fixes #53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants