dcm4chee-arc is gathering the records of different patients #3084
Answered
by
vrindanayak
andersoncav
asked this question in
Q&A
-
same patient id. dcm4chee-arc is gathering the records of different patients. is there any configuration in dcm4che-arc that block or create separate exams? please, could someone help me solve the problem |
Beta Was this translation helpful? Give feedback.
Answered by
vrindanayak
Mar 15, 2021
Replies: 4 comments 1 reply
-
Beta Was this translation helpful? Give feedback.
0 replies
Answer selected by
vrindanayak
-
sorry, i'm new to dcm4chee-arc.
please could you guide me the way where i can register this rule
dcmAcceptConflictingPatientID
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
Livre
de vírus. www.avast.com
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>.
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
Em seg., 15 de mar. de 2021 às 12:47, Vrinda ***@***.***>
escreveu:
… You may choose to either :
- Optionally validate Patient Attributes of received instances against
Patient Attributes in previous received instances of the Patient
<#1990> by
configuring Reject Conflicting Patient Attribute(s)
<https://dcm4chee-arc-cs.readthedocs.io/en/latest/networking/config/archiveNetworkAE.html#dcmrejectconflictingpatientattribute>
- Optionally use all Patient attributes for identifying Patients
without Issuer of Patient ID
<#2851> by
configuring Identify Patient by all Attributes
<https://dcm4chee-arc-cs.readthedocs.io/en/latest/networking/config/archiveDevice.html#dcmidentifypatientbyallattributes>
- Optionally validate Patient ID of received instances against the
Patient ID in previous received instances of the Study
<#506> by
configuring Accept Conflicting Patient ID
<https://dcm4chee-arc-cs.readthedocs.io/en/latest/networking/config/archiveNetworkAE.html#dcmacceptconflictingpatientid>
value to NO
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#3084 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADUPRQSVEJS5PKFKEFVIDUDTDYT2JANCNFSM4ZGZZ2GQ>
.
|
Beta Was this translation helpful? Give feedback.
1 reply
-
I applied the Accept Patient in Conflict rule, but it doesn’t work the
patients have different names but the patient ids are the same.
Is there a possibility that dcm4chee-arc does not group studies with
the same patient id?
Em seg., 15 de mar. de 2021 às 13:37, Vrinda ***@***.***>
escreveu:
… If you already have an archive running,
- Go to Configuration page -> Devices tab -> Select dcm4chee-arc device
- Go upto its Archive Device Extension and search for Accept
Conflicting Patient ID and change the value from default MERGED to NO
[image: image]
<https://user-images.githubusercontent.com/15785031/111188220-1d2d1280-85b5-11eb-88a7-cd38c7f8c4b8.png>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#3084 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADUPRQQALZHEETPQGYGOBE3TDYZWPANCNFSM4ZGZZ2GQ>
.
|
Beta Was this translation helpful? Give feedback.
0 replies
-
thanks,
I already managed, follow the link below that I used to fix
#1991
Em seg., 15 de mar. de 2021 às 15:05, Anderson Sousa ***@***.***>
escreveu:
… I applied the Accept Patient in Conflict rule, but it doesn’t work the patients have different names but the patient ids are the same.
Is there a possibility that dcm4chee-arc does not group studies with the same patient id?
Em seg., 15 de mar. de 2021 às 13:37, Vrinda ***@***.***>
escreveu:
> If you already have an archive running,
>
> - Go to Configuration page -> Devices tab -> Select dcm4chee-arc
> device
> - Go upto its Archive Device Extension and search for Accept
> Conflicting Patient ID and change the value from default MERGED to NO
>
> [image: image]
> <https://user-images.githubusercontent.com/15785031/111188220-1d2d1280-85b5-11eb-88a7-cd38c7f8c4b8.png>
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <#3084 (reply in thread)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ADUPRQQALZHEETPQGYGOBE3TDYZWPANCNFSM4ZGZZ2GQ>
> .
>
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
You may choose to either :
NO