MedQuist highlights StructuRad integration
MedQuist, a provider of clinical documentation workflow technology and services, highlighted its partnership with StructuRad to integrate and use StructuRad’s radiology reporting content “macros” in MedQuist’s SpeechQ for Radiology speech recognition solution product during the 2008 Society of Imaging Informatics in Medicine (SIIM) meeting in Seattle.

The purpose of the agreement is to provide a new add-on capability for macro reporting within SpeechQ. The SpeechQ macro reporting product will use content macros derived from StructuRad’s proprietary knowledge base radiology lexicon, according to MedQuist.

"For us the partnership is a really good marriage," Chris Spring, MedQuist director of speech recognition solutions, told Health Imaging News. “Obviously speech recognition is maturing—StructuRad takes it one step further.”

“One of the biggest benefits of speech recognition is community standardization and with StructuRad macros, we are able to embed referring physician content into SpeechQ,” he added.

Combining StructuRad macros with MedQuist’s advanced speech recognition solutions will further enhance SpeechQ users’ productivity, and make it easy for SpeechQ users to quickly create reports from an extensive library of templates, rather than developing them on their own. StructuRad currently has a library of more than 7,000 report templates, according to Spring.

Another new development MedQuist showcased during the show was improvements to software development kits for vendors. “We live at the desktop,” Spring said. “With these improvements, administrators can control PACS from SpeechQ now.”

Radiologists working within SpeechQ can access PACS from the program to view films and pull reports. “If you are working in SpeechQ and you want to save a presentation state, you can save it from SpeechQ to PACS,” he added.

“We will see more of an influx of software that is becoming a clinical information sharing hub,” he concluded. “It is not about RIS-driven workflow, or PACS-driven workflow anymore – it is about workflow-driven workflow.”