MTVIMP
Imports voice job and determines whether job is eligible for sending over to Concord. If so, it assigns the job to ZCVR.
MTVRSVR
Looks for jobs assigned to ZCVR. Then does a “check out” of the job
Creates a .request file for MTCCSVR to submit the job to Concord
MTCCSVR
Looks for .request files in voicerec\Concord\\job folder
Opens the .request file to get all the information about the job
Calls MTConcord to send job to Concord
MTConcord
.Net program to send jobs to Concord
Renames the .request to .inprocess file
Sends the audio job to Concord using a Web Service. This will wait for an acknowledgement that the job was received by Concord, but does not wait for jobs to be processed.
Creates a .done file and deletes the .inprocess file.
MTCCSVR
Looks for .done files in the voicerec\Concord\\job folder.
Creates a .response and a .bck file from the .done file (The .bck is to ensure MTVRSVR sees a .response file)
MTVRSVR
Looks for .bck file that does not have a matching .response file. If found, copies the .bck to a .response file.
Looks for and reads the .response file created by MTCCSVR
Updates the VOICE.ADT record with the job ID from Concord
Deletes the .bck and .response files
MTVRSVR
Sends .request files to MTCCSVR to get status of jobs that were previously submitted
MTCCSVR
Reads the .request files in the voicerec\Concord\status folder
Calls MTConcord.exe to get the status of the job
MTConcord
.Net program to get status information from Concord and retrieve draft reports
Renames the .request to .inprocess file
Will make web service call to Concord asking for the status of a job
If the status is complete, then it retrieves the “draft” report from Concord
If the author is still in training, then it retrieves a “blank” document for the job. This document file is just a skeleton file that contains various ID’s. Eventually the blank document is used for typing a report from scratch.
Creates a .done file to send the status of the job back to MTCCSVR
MTCCSVR
Reads the .done file created by MTConcord
Renames it .response file with the job status for MTVRSVR
MTVRSVR
Reads the .response file and gets the job status
If the status is complete and we received draft report, then the draft report is imported into the ChartNet system and placed on the VRDRAFT review queue.
If the author is still in training then the “blank” report comes back. MTClient will allow the MT to type the report from scratch.
If the status is such that it is still being processed by Concord, then the program will wait 1 a few minutes before sending another status .request to MTCCSVR.
MTCLIENT
The draft report is now in ChartNet and can be reviewed in the Concord Editor.
Action to trigger rendering (i.e. Review Complete)
MTREQSVR
The uMisc.SendReportToHost routine files the report back into the database
If the Reports.Render flag is TRUE, then it creates a file for MTRENDER to process
Creates a .key file for MTUPDATE to process and update the database tables
MTRENDER
Looks for files to process
Creates a .request file for MTConcorr2RTF indicating what report to render
MTCONCORD2RTF
Looks for .request files to process
Renders the CDA/XML file to RTF
Creates a .response file to MTRENDER
MTRENDER
Reads the .response file
Imports the rendered RTF file into the report’s database
Uses the Workflow table to determine what action to take next
MTUPDATE
Reads the .key files created by MTREQSVR
Updates the STATS table
Calls the ExportReportToVRVendor routine
All VR job will be sent to Concord for continuous training of the author
Creates an .exp file for MTVRSVR to read
MTVRSVR
Reads the .exp files created by MTUPDATE
Creates a .request file for MTCCSVR to send finalized document (.XML) back to Concord
MTCCSVR
Reads the .request file
Calls MTConcord
MTCONCORD
.Net program to send finalized documents back to Concord
Renames the .request to .inprocess file
Creates a .done file for MTCCSVR
MTCCSVR
Looks for a .done file and renames it to a .response file for MTVRSVR
MTVRSVR
Reads the .response file created by MTCCSVR
Updates the database