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-67 response (and elsewhere?) location of pointer to StructureDefinition #72

Closed
lynnfel opened this issue Apr 30, 2021 · 1 comment
Closed
Assignees
Labels
bug Something isn't working the way intended. header num Problem caused by header number failure in the IG builder
Milestone

Comments

@lynnfel
Copy link
Contributor

lynnfel commented Apr 30, 2021

Section Number https://profiles.ihe.net/ITI/MHD/ITI-67.html#resource-bundling
and similar message semantics sections elsewhere.

Issue
(1) This Resource Bundling section contains Document Location
(2) The Document Location text (specifying the URL) contains a pointer to the Structure Definition

Proposed Change
(1) Make "Document Location" its own section heading at the same level as the previous "Resource Bundling" section"
(2) Move this sentence "An informative StructureDefinition is outlined for MHD Find Document References Comprehensive Response Message, with an example." to the end of Message Semantics https://profiles.ihe.net/ITI/MHD/ITI-67.html#message-semantics-1.
(2a) For consistency, in transaction message semantics for both request and response, the last sentence could be a pointer to the informative StructureDefinitions, or at the end of message semantics, we create a subheading "Informative StructureDefinition" which would made this a template-able consistency. (This is similar to what you have done in adding the "CapabilityStatement Resource" sub-section to the transactions)

Priority:

  • Low: Typo or other minor classification that an editor can manage. Requires no group discussion.
@JohnMoehrke JohnMoehrke added header num Problem caused by header number failure in the IG builder bug Something isn't working the way intended. labels May 5, 2021
@JohnMoehrke JohnMoehrke added this to the 4.0.0 milestone May 5, 2021
@JohnMoehrke
Copy link
Contributor

(1) should be a header 7, but header 7 does not exist in markdown or html
(2) most of the message semantics are encoded in the structure definition. So it should be seen as the primary definition of the message semantics. Thus it should not be seen as a sub-header, or as secondary. Will look to make this more clear and consistent.

@JohnMoehrke JohnMoehrke self-assigned this May 5, 2021
JohnMoehrke added a commit that referenced this issue May 5, 2021
…sing #71, closing #70, closing #69, closing #65, closing #17, closing #39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working the way intended. header num Problem caused by header number failure in the IG builder
Projects
None yet
Development

No branches or pull requests

2 participants