Engaging Conversations on Healthcare and Technology

  • TwitterFacebookRSS

Interoperability, RSNA, and Standards – What Do They Have in Common?

Integrating the Healthcare Enterprise (IHE) is driving the use of standards forward to solve healthcare integration challenges. At RSNA, IHE has developed healthcare interoperability demonstrations that illustrate how integrated radiology workflows can work between institutions and applications.

Health Imaging & IT published an article entitled New Standards to Help with Interoperability about how DICOM and HL7 Clinical Document Architecture (CDA) work together to solve healthcare integration issues. As the article states, “Since referring physicians commonly use systems with HL7 rather than DICOM capabilities, DICOM and HL7 working groups recognized the need to work together to define a standard methods for reporting that meet the needs of the real worlds.”

When a radiologist receives an order to render an interpretation, the clinical history of the patient started before that order was generated. The clinical history typically will be recorded as a text-based file in a physician’s office. For the radiologist to have the patient’s complete health picture, the clinical data required for the order and the ultimate patient report needs to be delivered electronically as text.

HL7 is the standard that delivers that patient’s clinical background to the radiologist. Incorporating the clinical data with images in one patient report can be accomplished by using the HL7 CDA or DICOM SR standards. Healthcare standards continue to offer choices to healthcare providers, which opens the door for inconsistency of clinical exchanges.

IHE is facilitating the discussion and adoption of standards for radiology practices. RSNA is one arena where these conversations are occurring between vendors and providers.

Related posts:

  1. HL7 2.X Interoperability and Conformance Profiles
  2. What Are the Different Standards in Healthcare?
  3. Increasing Radiologist Efficiency and Productivity
  4. Embedding or Sending a CCR Document Inside an HL7 2.X Message
  5. What Is an ORM Message?
  • http://hl7standards.com/blog/2006/11/30/all-healthcare-integration-is-local/ All Healthcare Integration Is Local – NeoTool Healthcare IT Blog

    [...] As we have discussed in previous RSNA posts, Integrating the Healthcare Enterprise (IHE) has had a major presence at the show. Yesterday, Nikolaus Wirsz, PhD, manager IT standards, Siemens Medical Solutions, gave a presentation entitled The IHE Initiative Worldwide: An Update. During the presentation, he stated “IHE is not a local problem; we are seeing integration problems everywhere. As a result, IHE has been promoted worldwide.” [...]

  • http://hl7standards.com/blog/2006/11/29/sharing-patient-information-and-images/ Sharing Patient Information and Images

    [...] the technology to share patient information and images is being demonstrated by vendors using the IHE integration profiles such as XDS-I (Cross-enterprise Document Sharing for Imaging). The profiles [...]

  • http://hl7standards.com/blog/2007/08/30/how-widely-adopted-is-hl7/ How Widely Adopted Is HL7?

    [...] standard” to use even if they just want “a little interfacing.” Standards profiling helps resolve this [...]

  • http://www.hl7standards.com/blog/2006/11/30/all-healthcare-integration-is-local/ All Healthcare Integration Is Local | HL7 Standards

    [...] we have discussed in previous RSNA posts, Integrating the Healthcare Enterprise (IHE) has had a major presence at the show. Yesterday, [...]

blog comments powered by Disqus