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

Endpoint.period MS constraint #154

Open
IrfanH99 opened this issue Jul 23, 2024 · 2 comments
Open

Endpoint.period MS constraint #154

IrfanH99 opened this issue Jul 23, 2024 · 2 comments

Comments

@IrfanH99
Copy link

Section: In the IHE mCSD iGuide version 3.8.0, Enpoint Profile

Issue: The pan-Canadian Care Services Directory (based on the mCSD) received pushback from vendors currently implementing endpoint on the use of the .period element and the strong mustSupport requirement placed on it. Through our discussion with the vendors, we learned that the use cases for this element are very niche and majority of the vendors do not see using it at all. With further discussions with IHE ITI WG members, we did not find its use to be major at an international level.

Proposed Change: A relaxation of the mustSupport constraint on this element is proposed.

Priority: Medium

@JohnMoehrke
Copy link
Contributor

Given that IHE uses "required if known" as our definition of MS. What is the concern? If you never have data to populate the element, then the implementation is indistinguishable from one in which the element is not tagged with MS.
Can you explain the negative you see with the current specification?

@lukeaduncan
Copy link
Contributor

Discussed today during face to face. Inclined to leave as is since mustSupport doesn't require use. One point is that if it is populated then it is very important. Counterpoint is that it's so rarely used it might be confusing.

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

No branches or pull requests

3 participants