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-104 resolve duplicates expected actions #29

Closed
lynnfel opened this issue Jul 21, 2021 · 2 comments
Closed

ITI-104 resolve duplicates expected actions #29

lynnfel opened this issue Jul 21, 2021 · 2 comments
Assignees
Labels
telco to be discussed

Comments

@lynnfel
Copy link
Contributor

lynnfel commented Jul 21, 2021

https://build.fhir.org/ig/IHE/ITI.PIXm/branches/master/ITI-104.html#23104423-expected-actions

The Patient Identifier Cross-reference Manager shall be capable of accepting attributes in the Duplicates Resolved message as specified in 3.104.4.2.2.2.1. <=== Not a valid section number

The Patient Identifier Cross-reference Manager shall perform the Expected Actions similar to the ones specified in ITI TF-2: 3.8.4.2.3. The particular behavior is described below. <=== if the expected actions are 'similar' but not the same, what is the value of the reference??

When the Patient Identifier Cross-reference Manager receives the Resolve Patient duplicate message of the Patient Identity Feed transaction, (<=== match the message name exactly) ...

... it shall cross-reference the patient identifiers provided by replacing any references it is maintaining internally to the patient identifier provided in the ‘replaces’ link by the patient identifier included in the Patient resource. After the identifier references are replaced, the Patient Identifier Cross-reference Manager shall reapply its internal cross-referencing logic/ policies before providing the updated information via the PIX Query transactions. (<=== in the beginning of this text, you say it shall cross-reference... but at the end, you say that the cross-referencing happens after the identifier references are replaced. I think this text needs revision in committee.)

@oliveregger
Copy link
Contributor

https://build.fhir.org/ig/IHE/ITI.PIXm/branches/master/ITI-104.html#23104423-expected-actions

The Patient Identifier Cross-reference Manager shall be capable of accepting attributes in the Duplicates Resolved message as specified in 3.104.4.2.2.2.1. <=== Not a valid section number

fixed with #15

The Patient Identifier Cross-reference Manager shall perform the Expected Actions similar to the ones specified in ITI TF-2: 3.8.4.2.3. The particular behavior is described below. <=== if the expected actions are 'similar' but not the same, what is the value of the reference??

good point, will remove the sentence

When the Patient Identifier Cross-reference Manager receives the Resolve Patient duplicate message of the Patient Identity Feed transaction, (<=== match the message name exactly) ...

... it shall cross-reference the patient identifiers provided by replacing any references it is maintaining internally to the patient identifier provided in the ‘replaces’ link by the patient identifier included in the Patient resource. After the identifier references are replaced, the Patient Identifier Cross-reference Manager shall reapply its internal cross-referencing logic/ policies before providing the updated information via the PIX Query transactions. (<=== in the beginning of this text, you say it shall cross-reference... but at the end, you say that the cross-referencing happens after the identifier references are replaced. I think this text needs revision in committee.)

also related to issue #16

@oliveregger oliveregger self-assigned this Jul 22, 2021
@oliveregger oliveregger added the question Further information is requested label Jul 22, 2021
oliveregger added a commit that referenced this issue Jul 22, 2021
@oliveregger oliveregger added telco to be discussed and removed question Further information is requested labels Jul 22, 2021
@oliveregger
Copy link
Contributor

last point will be closed with #16

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
telco to be discussed
Projects
None yet
Development

No branches or pull requests

2 participants