DocScanFx supports launching directly from a PACS, Radiology Information System (RIS), or an Electronic Medical Record (EMR) in order to pass a patient in context to DocScanFx and eliminate the need to search for a patient’s exam a second time.  The four different launch options are described below.  Contact PacsLogic Support for more information on configuring these options with your application.


Note that the executable 'dsTrigger.exe' is used for integrating to DocScanFx in all the examples shown below.  After a normal install of DocScanFx this file is in the \DocScanFx\Resources folder and must be moved up one level to the DocScanFx folder.


Method 1 - Direct Launch: 

This integration option requires the PACS / RIS / EMR application to pass all 14 data patient/exam related data fields shown below as command line arguments to the dstrigger.exe process in the DocScanFx install folder.  No DICOM query is necessary.  This action should be initiated when an end users clicks a button or other similar action in the originating application to start DocScanFx in the context of the currently open or selected imaging study. Note that the field "{{{DSFX Mode}}}" is optional and is used to force DocScanFx into a particular scanning “mode”.


Example with DICOM tag values:

C:\Program Files (x86)\DocScanFx\dsTrigger.exe "{0008,0020}" "{0008,0030}" "{0008,0050}" "{0008,0060}" "{0010,0040}" "{0008,0090}" "{0008,1030}" "{0010,0010}" "{0010,0020}" "{0010,0030}" "{{{DSFX Mode}}}" "{0020,000d}" "" "{0032,1030}" "{0020,0010}"


Example with field descriptions:

C:\Program Files (x86)\DocScanFx\dsTrigger.exe "{StudyDate}" "{StudyTime}" "{AccessionNumber}" "{Modality}" "{PatientSex}" "{ReferringPhysiciansName}" "{StudyDescription}" "{PatientName}" "{PatientID}" "{PatientBirthDate}" "{{{DSFX Mode}}}" "{StudyInstanceUID}" "" "{Reason for Study}" "{Study ID}"


With Additional mode INI option:

ModeWorkflow=Integrated



Method 2 - Direct Launch with Accession or Study Instance UID (SIUID) Only:

 This integration option requires the PACS / RIS / EMR application to either pass the Accession number or the SIUID as a command line argument to the dstrigger.exe process in the DocScanFx install folder.  This action should be initiated when an end users clicks a button or other similar action in the originating application to start DocScanFx in the context of the currently open or selected imaging study.  This requires DocScanFX to perform a DICOM query for the missing patient/exam data elements and also requires the PACS archive to be able to return all the required values.   Note that the second command line argument shown below (mode="Documents") is optional and is used to force DocScanFx into a particular scanning “mode”.


Example with SIUID:

C:\Program Files (x86)\DocScanFx\dsTrigger.exe StudyInstanceUID=1.2.826.0.1.10.62746 mode="Documents"


With additional mode INI options:
ModeWorkflow=Integrated
IntegrationQueryMissingValues=True
IntegrationQueryMissingValuesTWithTag=SIUID


 

Example with Accession:

C:\Program Files (x86)\DocScanFx\dsTrigger.exe Accession=ACC23239310 mode="Documents"

With additional mode INI Options:

ModeWorkflow=Integrated
IntegrationQueryMissingValues=True
IntegrationQueryMissingValuesTWithTag=Accession



Related INI Option Descriptions:

  • IntegrationQueryMissingValues: [True* / False]
    • If DocScanFx is setup to integrate with a PACS or RIS, then the PACS/RIS is expected to send an XML file to DocScanFx which contains all the patient/exam demographics needed to create the new images.  If this value is set to True and only a Study Instance UID is sent in the XML file, then DocScanFx will use the specified mode’s DICOM settings to attempt to query the archive or worklist for all the other needed patient and exam values.
  • IntegrationQueryMissingValuesTWithTag:[SIUID*/Accession]
    • In integrated mode if certain required patient or exam values are missing this option decides whether DocScanFx will perform a query using an accession number or the Study Instance UID to find the missing values.
  • IntegrationExitOnFailedMissingValues: [True/ False]
    • If the IntegrationQueryMissingValues is set to True and it fails to retrieve the required values, this setting decides if DocScanFx should exit or prompt the user to manually add the missing values.  Defaults to True if no responses are found.  Defaults to False if some responses are found but exam still fails validation (still missing some required values).




Method 3 - XML Folder Watch: 

This integration option requires the PACS / RIS / EMR application to write an XML file containing the 15 data patient/exam related data fields shown below.  No DICOM query is necessary.  The creation of this XML file should occur when an end users clicks a button or other similar action in the originating application to start DocScanFx in the context of the currently open or selected study.  Note that "Mode" and "TechInitials" are optional fields.  If this exact XML format is not possible, DocScanFx has mapping options to find the needed data fields in alternative XML locations.  Note that XML integration require running a background process in order to watch a folder for new XML files.  Please contact support@PacsLogic.com for more information on using this integration.

 

Example XML:

<DocScanXML>

       <Mode>VRAD Prelim</Mode>

       <Patient>

              <PatientName>SMITH^JOHN^M^Rev.^Jr.</PatientName>

              <PatientID>00123456789</PatientID>

              <PatientDOB>19010203</PatientDOB>

              <PatientSex>M</PatientSex>

       </Patient>

       <Exam>

              <StudyDate>20150101</StudyDate>

              <StudyTime>010101</StudyTime>

              <Accession>A11111</Accession>

              <Modality>CR</Modality>

              <ReferringPhysician>Onelittle^Sam^B^^M.D.</ReferringPhysician>

              <StudyDescription>XR Chest 1 Views PA</StudyDescription>

              <TechInitials>MLG</TechInitials>

              <StudyID>1234</StudyID>

              <StudyInstanceUID>123.456.789.1</StudyInstanceUID>

              <StudyReason>Chest Pain</StudyReason>

       </Exam>

</DocScanXML>


XML Folder Watch INI options (see “DocScan INI Settings v3.x.x.x” documentation for more details):

MonitoredFolder

FolderRecheckTime

FileToWatch

ForceMode




Method 4 - XML Folder Watch with Study Instance UID (SIUID) only: 

This integration option requires the PACS / RIS / EMR application to write an XML file containing only the Study Instance UID of the exam.  The creation of this XML file should occur when an end users clicks a button or other similar action in the originating application to start DocScanFx in the context of the currently open or selected study.  This requires DocScanFX to perform a DICOM query for the missing patient/exam data elements and also requires the PACS archive to be able to return all these missing values.  Note this method introduces a small delay to the end user while DocScanFx is retrieving the information (typically 1-3 seconds).  If this exact XML format is not possible, DocScanFx has mapping options to find the SIUD in an alternative XML location.  Note that XML integration require running a background process in order to watch a folder for new XML files. See the “DocScan INI Settings v3.0.x.x” documentation for more details.


Example XML:

<DocScanXML>

       <Exam>          

              <StudyInstanceUID>1.2.826.0.1.368.1.3.2.8.158.302020</StudyInstanceUID>

       </Exam>

</DocScanXML>


XML Folder Watch SIUID only INI options (see “DocScan INI Settings v3.x.x.x” documentation for more details):

MonitoredFolder

FolderRecheckTime

FileToWatch

ForceMode

IntegrationQueryMissingValues

IntegrationExitOnFailedMissingValues