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

Transaction Optionality #92

Open
slagesse-epic opened this issue Jul 22, 2023 · 3 comments
Open

Transaction Optionality #92

slagesse-epic opened this issue Jul 22, 2023 · 3 comments
Labels
open-issue Documented as an Open-Issue

Comments

@slagesse-epic
Copy link
Member

Currently we are mandating that Patient Demographics Suppliers support both ITI-78 and ITI-119, while Patient Demographics Consumers have the option to choose to support either one or both transactions. Is requiring support for both transactions a problem for any Patient Demographics Suppliers? We note that prior versions of the specification included only ITI-78, meaning this is new functionality existing suppliers will need to incorporate. Do we want named options here?

@slagesse-epic slagesse-epic added the open-issue Documented as an Open-Issue label Jul 22, 2023
@RicardoQuintano
Copy link

My opinion is NOT to mandate both of them. I think the Suppliers could implement these transactions based on their use case demands/needs.

@slagesse-epic slagesse-epic added the needs discussoin request for broader examination in committee label Feb 3, 2024
@slagesse-epic
Copy link
Member Author

Add option for $match.

@slagesse-epic slagesse-epic self-assigned this Feb 5, 2024
@slagesse-epic slagesse-epic removed their assignment Feb 6, 2024
@slagesse-epic slagesse-epic removed the needs discussoin request for broader examination in committee label Feb 6, 2024
@slagesse-epic
Copy link
Member Author

Will leave the issue open to allow for further comment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
open-issue Documented as an Open-Issue
Projects
None yet
Development

No branches or pull requests

2 participants