Hi,

When I send a mammography image for presentation to DVT with a L-MLO view I get an error stating that the “Patient Orientation” (0020,0020) which has the value “A”,”FR” is incorrect. FR is apparently for part of the list of enumerated values.
However, DICOM states in part 3 C.7.6.1.1.1 Patient Orientation that:

For Patient Orientation each value of the orientation attribute shall contain at least one of the abbreviations. If refinements in the orientation descriptions are to be specified, then they shall be designated by one or two additional abbreviations in each value. Within each value, the abbreviations shall be ordered with the principal orientation designated in the first abbreviations.

See also note 2 that states:

E.g., a medio-lateral oblique projection of the left breast of a human might be encoded with Patient Orientation values of “A\FR” rather than “A\F”, since the plane is obliquely inclined such that the colums are directed both downwards and medially, which for a left breast is towards the right, though the downwards direction is the principal column orientation.

Is there a way to work around this problem in DVT?

Best regards

Ludo

Does anybody has the code to replicate Sync StorageCommit and Async StorageCommit functionality using dvtk sdk APIs?

Hi,

When I send a Grayscale Softcopy Presentation State object to DVT, containing a Bitmap Display Shutter Module (To hide the background of a mammo image), then DVT give’s me back an error that has to do with the "Display Shutter Module".
DVT complains that 0018,1600 Shutter Shape hast the wrong value (= Bitmap).

Below this, in the "Bitmap Display Shutter Module" the same attribute 0018,1600 Shutter Shape with value =Bitmap is indicated as correct. (As expected)

Is this a known problem?

Best regards,

Ludo

Hi Marco,

Did someone already create a ticket for this problem and if yes, what is the status today?

Regards,

Ludo

Hello,
to test our StorageCommitmentSCP we would like to validate the response if the storage commitment fails. The script is attached.
The problem is, that even if the response is negative, DVT wants the ReferencedSOPSequence. In our research in the DICOM standard we came across PS 3.4-2008, Page 174.:
"When a response is negative the field "Referenced SOP Sequence", is not mandatory and should be present only when there is any positive match"

But when running the script, the result is "failed" and DVT says:
"Type 1 (mandatory) attribute (0008,1199) should be present with at least one value."

I have tried the latest DVT version 2.6.8. Is this a bug in DVT or a problem in our script?

Thank you very much!

Attach file:

---

failed_storage_commitment.ds.zip Size: 0.66 KB; Hits: 93

below is the result from DTV, I am clueless where is the error.
- I have created project.
- I have created session, correctly selected Definitions folder + manually selected FileMeta.def and ModalityPerformedProcedureStep.def.
And tried to validate MPPS N-CREATE or N-SET datasets from local drive.

and simply DVT tool fails each time to recognize MPPS Sop Class !??
Any clues why this isn't working?
------------------------------------------------------------------

Session Details
Session ID: 0
Session Title: MPPS
Application Entity Name: DICOM
Application Entity Version: 3.0
Tester: Administrator
Test Date: 01/03/2013 14:45:53

File Meta

Module: Dicom Meta Information (M)
Attribute Def VR Dcm VR Type Pr Len Attribute Name Value(s) and Comments
(0002,0002) UI UI 1 + 24 Media Storage SOP Class UID 1.2.840.10008.3.1.2.3.3


Warning: Attribute (0002,0002) value "1.2.840.10008.3.1.2.3.3" not in list of defined terms list
Link to Detailed Result


Selected Dataset definition: "File Meta". Using AE Name "DICOM" - AE Version "3.0"



Warning: Could not find Dataset definition for SOP UID: "1.2.840.10008.3.1.2.3.3", Dimse: C-STORE-RQ Using Definitions with AE Name "DICOM" - AE Version "3.0"

Hi David,

thanks for the info.
I'm not aware of a any adjustment needed to compile under Windows 7...
Maybe another user can give some advice.

What is the reason you are trying to recompile the library?

Regards,
Marco

Hi David,

thanks for letting other people know the space problem so fast.

Regards,
Marco

So building on windows 7 will remain a mystery. Make sure you let every one know.