RetroBBS - comp.protocols.dicom

Fixing Mistakes

<eda28299-aa4d-47d8-ba1b-9a4ba74c44acn@googlegroups.com>

https://www.rocksolidbbs.com/devel/article-flat.php?id=701&group=comp.protocols.dicom#701

copy link Newsgroups: comp.protocols.dicom

X-Received: by 2002:ac8:5dc8:0:b0:3f4:b1bd:c30e with SMTP id e8-20020ac85dc8000000b003f4b1bdc30emr6582442qtx.8.1684238196262;
Tue, 16 May 2023 04:56:36 -0700 (PDT)
X-Received: by 2002:a05:620a:1994:b0:74d:f7d0:6a5f with SMTP id
bm20-20020a05620a199400b0074df7d06a5fmr10751016qkb.0.1684238195990; Tue, 16
May 2023 04:56:35 -0700 (PDT)
Path: i2pn2.org!i2pn.org!usenet.blueworldhosting.com!diablo1.usenet.blueworldhosting.com!peer01.iad!feed-me.highwinds-media.com!news.highwinds-media.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.protocols.dicom
Date: Tue, 16 May 2023 04:56:35 -0700 (PDT)
Injection-Info: google-groups.googlegroups.com; posting-host=165.225.62.10; posting-account=wXdxgQoAAACjfTn9FxEbewrGAWOkt_h-
NNTP-Posting-Host: 165.225.62.10
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <eda28299-aa4d-47d8-ba1b-9a4ba74c44acn@googlegroups.com>
Subject: Fixing Mistakes
From: eulalie7@gmail.com (Eulalie)
Injection-Date: Tue, 16 May 2023 11:56:36 +0000
Content-Type: text/plain; charset="UTF-8"
X-Received-Bytes: 1471

by: Eulalie - Tue, 16 May 2023 11:56 UTC

Is there a provision in the standard for fixing mistakes made at the modality?

Scenario:

EMR provides DMWL
Orders are not send to PACS

Tech chooses accession 09 instead of accession 10 off the DMWL
Tech performs the correct procedure on the correct patient and sends images to PACS
Tech modifies the images from 09 to 10 in PACS
Tech completes 10 in EMR
2nd patient comes in and tech chooses accession 09 off the DMWL

For this scenario, how does the standard get applied in this scenario?

Re: Fixing Mistakes

<954f02df-dd72-4b4c-bbda-9dfa8bfaf494n@googlegroups.com>

copy mid

https://www.rocksolidbbs.com/devel/article-flat.php?id=702&group=comp.protocols.dicom#702

copy link Newsgroups: comp.protocols.dicom

X-Received: by 2002:a05:622a:105:b0:3e4:e17f:a544 with SMTP id u5-20020a05622a010500b003e4e17fa544mr14164637qtw.12.1684312062647;
Wed, 17 May 2023 01:27:42 -0700 (PDT)
X-Received: by 2002:a05:622a:1999:b0:3f3:6708:c7cc with SMTP id
u25-20020a05622a199900b003f36708c7ccmr14704834qtc.0.1684312062411; Wed, 17
May 2023 01:27:42 -0700 (PDT)
Path: i2pn2.org!i2pn.org!usenet.blueworldhosting.com!diablo1.usenet.blueworldhosting.com!peer03.iad!feed-me.highwinds-media.com!news.highwinds-media.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.protocols.dicom
Date: Wed, 17 May 2023 01:27:42 -0700 (PDT)
In-Reply-To: <eda28299-aa4d-47d8-ba1b-9a4ba74c44acn@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=80.150.143.228; posting-account=jCznZwoAAAAUnErZ3tGh5T1VmczStXTP
NNTP-Posting-Host: 80.150.143.228
References: <eda28299-aa4d-47d8-ba1b-9a4ba74c44acn@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <954f02df-dd72-4b4c-bbda-9dfa8bfaf494n@googlegroups.com>
Subject: Re: Fixing Mistakes
From: detlev.stalling@gmail.com (Detlev Stalling)
Injection-Date: Wed, 17 May 2023 08:27:42 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Received-Bytes: 2320

by: Detlev Stalling - Wed, 17 May 2023 08:27 UTC

On Tuesday, May 16, 2023 at 1:56:37 PM UTC+2, Eulalie wrote:
> Is there a provision in the standard for fixing mistakes made at the modality?
>
> Scenario:
>
> EMR provides DMWL
> Orders are not send to PACS
>
> Tech chooses accession 09 instead of accession 10 off the DMWL
> Tech performs the correct procedure on the correct patient and sends images to PACS
> Tech modifies the images from 09 to 10 in PACS
> Tech completes 10 in EMR
> 2nd patient comes in and tech chooses accession 09 off the DMWL
>
> For this scenario, how does the standard get applied in this scenario?

Ideally, incorrect images should be invalidated via KOS objects following the IOCM workflow. The problem is that when images are fixed in the PACS (with or without IOCM), often the correct Study Instance UID for accession 10 is not known. Some PACS invent a new SUID in order to avoid conflicts with the yet-to-be-performed accession 09. If the SUID is kept and later reused for accession 09, usually the 09 images would be rejected or end up in a dirty area in the PACS.
Detlev

"Nuclear war can ruin your whole compile." -- Karl Lehenbauer

devel / comp.protocols.dicom / Fixing Mistakes

Subject	Author
Fixing Mistakes	Eulalie
Re: Fixing Mistakes	Detlev Stalling