DICOM Correction Proposal



Similar documents
Digital Imaging and Communications in Medicine (DICOM) Part 20: Transformation of DICOM to and from HL7 Standards

MDHT Capabilities & Success Story

Quality, Research and Public Health (QRPH) Technical Framework Supplement. Physician Reporting to a Public Health Repository Cancer Registry (PRPH-Ca)

Implementation Guide for Study Design Structured. Document. FDA Guidance for Human Clinical Trials

Cancer Reporting Errata and Clarification Document for Electronic Health Record (EHR) Technology Certification December 2012

IHE Pharmacy Technical Framework Supplement. Pharmacy Medication List (PML) Trial Implementation

IHE Radiology Technical Framework Supplement. Clinical Decision Support Order Appropriateness Tracking (CDS-OAT) Trial Implementation

DRAFT CMS Implementation Guide for Quality Reporting Document Architecture Category I and Category III

HL7 CDA (Clinical Document Architecture) in Structured Diagnostic Reporting

CDX Conformance Profile EMR System Conformance CDA Level 1

CMS Implementation Guide for Quality Reporting Document Architecture Category I and Category III

HL7 Clinical Genomics and Structured Documents Work Groups

Goals. Accelerating adoption & exchange of EHRs project. Evaluation Indicators EMR adoption (Hospitals) 20% (100 hospitals)

Clinical Interoperability to Improve Quality and the Point-of-Care of EHR

Interoperabilidad entre los Sistemas de Laboratório Clinico

Michigan Birth Defect Registry

Interoperability and Integrating the Healthcare Enterprise

20/20 Integration Guide

HL7 Interface Specification. HL7 Interface 1.2

Adoption of HL7 Standards in Taiwan

Implementation Guide for CDA Release 2 Genetic Testing Report (GTR)

HL7 Clinical Document Architecture: Overview and Applications

MFI 4 Extended Registry SC32/WG2

HL7 & HL7 CDA: The Implementation of Thailand s Healthcare Messaging Exchange Standards Nawanan Theera-Ampornpunt, M.D., Ph.D.

HEALTH INFORMATION STANDARDS COMMITTEE FOR ALBERTA

Unobtrusive fall detection and sensor system interoperability for telemonitoring

Meaningful Use Stage 2 Update: Deploying SNOMED CT to provide decision support in the EHR

Electronic Health Network - Case Study Consent2Share Share with Confidence

Implementation Guide for CDA Release 2.0 Progress Note (U.S. Realm) Draft Standard for Trial Use Levels 1, 2, and 3 First Ballot September 2010

OpenEMR: Achieving DICOM Interoperability using Mirth

HL7v3, the vocabulary. Marc de Graauw

JiveX Enterprise PACS Solutions. JiveX HL7 Gateway Conformance Statement - HL7. Version: As of

DICOM Structured Reporting Overview

PARCA Certified PACS Interface Analyst (CPIA) Requirements

Introduction to Epic Bridges. Empowering Extraordinary Patient Care

Implementing a SAS Metadata Server Configuration for Use with SAS Enterprise Guide

Interdependent Registries - Domain Analysis Model (DAM)

DIAGNOSTIC TEXT AND OTHER TRANSCRIBED REPORTS MESSAGE SPECIFICATION

DICOM Correction Proposal

NH CHIS Annual Meeting. Thursday, July 25, :00am 11:30am EDT In-person (NH DHHS Brown Building Auditorium) and WebEx

ACR Triad Site Server Click Once Software System

IHE IT Infrastructure Technical Framework Supplement. Document Digital Signature (DSG) Trial Implementation

DICOM Conformance Statement FORUM

How To Get A Medical Record On A Medical Device

Structured Data Capture (SDC) The Use of Structured Data Capture for Clinical Research

The Continuity of Care Document. Changing the Landscape of Healthcare Information Exchange

SMART C CDA Collaborative Perspective & Debriefing

HL7 Customization Guide

Electronic Data Interchange (EDI) Registration for Oregon Medicaid

IHE Patient Care Coordination (PCC) Technical Framework Supplement. Referral/Order Linking (ROL) Trial Implementation

ShadowLink 2. Overview. May 4, ONLINE SUPPORT emdat.com/ticket/ PHONE SUPPORT (608) ext. 1

AIDA compact NEO HL7 Interface Description

Impact of Electronic Health Records Implementation on the Early Detection Hearing and Intervention Programs

ELR Clarification Document for EHR Technology Certification

LIS Interfaces: Basics, Implementation and Pitfalls

ImagePilot. HL7 Conformance Statement. Manufacturer: 1 Sakura-machi, Hino-shi Tokyo , Japan

Tools for DICOM Implementation

Structured Data Capture (SDC) Trial Implementation

CDA for Common Document Types: Objectives, Status, and Relationship to Computer-assisted Coding

ISO 9001: 2008 Construction Quality Management System Sample - Selected pages (not a complete plan)

HL7 Conformance Statement

Model-Driven Health Tools (MDHT) CDA Tools Overview.

HL7 IHE SNOMED DICOM

NSI XML Retail Accounting Report Consuming Application 1.0 Conformance Statement

IHE Radiology Technical Framework Volume 3 (IHE RAD TF-3)

Integrating Patient Care & Research Information Systems «ORBIS Research»

HL7 Draft Standard for Trial Use

Webinar Overview. OPA s FPAR 2.0 Goals & Strategy Update on 2.0 Activities & Progress Review 2.0 tentative timeline

Measure #195 (NQF 0507): Radiology: Stenosis Measurement in Carotid Imaging Reports National Quality Strategy Domain: Effective Clinical Care

TechNote. Enterprise EMR Integration. 1 Overview. 2 DR Systems Integration with Referring Physician EMR Systems

Table of Contents. 1. Software House Website Login. a. Forgot My Password Recovery Feature. 2. Site Registration. a. Creating Your Account

Transcription:

DICOM Correction Proposal Status Assigned Date of Last Update 2015/03/23 Person Assigned Submitter Name Harry Solomon Harry Solomon Submission Date 2015/03/23 Correction Number CP-1484 Log Summary: Add ordering decision support to CDA Name of Standard PS3.20 2015b Rationale for Correction: Extracted from Sup 155 LB, at request of WG6. Adds structured entry for documentation of clinical decision support, to utilize data elements as required by U.S. (and other) regulation, and harmonized with IHE Radiology profile. Correction Wording: Add the following structured entry to the Request subsection 9.8.1 Request > entry 0..* MAY CDSRecordE ntry[*] >> observation 1..1 SHALL >>@ @classcode 1..1 SHALL CS SHALL OBS >>@ @moodcode 1..1 SHALL SHALL EVN SessionID >>> id 1..1 SHALL II OBX-21, >>> code 1..1 SHALL CD SHALL (76515-6, LOINC, Requested Procedure is Appropriate ) Page 1

CDSDecision >>> value 1..1 SHALL CD SHALL ValueSet LOINC Y/N/NA 1.3.6.1.4.1.12 009.10.1.163 >>>@ @xsi:type 1..1 SHALL ST SHALL CD OBX-5, where OBX-3 = 76515-6^LN >>> statuscode 1..1 SHALL CS SHALL COMPLETED CDSDecision Time CDSDecision Criteria >>> effectivetime 0..1 SHOULD TS >>> methodcode 0..1 MAY CD ConceptDom ain AppropriateUs ecriteria OBX-17, >>> text 0..1 SHOULD ED Ref >>>> reference 1..1 SHALL URL (XML IDREF) #contentref >>> author 1..1 SHALL >>>> assignedauthor 1..1 SHALL CDSServiceI D id 1..1 SHALL II OBX-15, > assignedauthoring Device 0..1 MAY CDSServiceN ame >> softwarename 1..1 SHALL ST >>> participant 1..1 SHALL >>>@ @typecode 1..1 SHALL CS SHALL REF >>>> participantrole 1..1 SHALL >>>>@ @classcode 1..1 SHALL CS SHALL PROV OrderingProv iderid id 1..1 SHALL II Ordering Provider ORC- 12.1 + ORC- 12.9.2 > >@ playingentity 0..1 MAY @classcode 1..1 SHALL CS SHALL PSN Page 2

OrderingProv idername >> name 1..1 SHALL PN Ordering Provider ORC- 12 >> entryrelationship 0..1 SHOULD >>@ @typecode 1..1 SHALL CS SHALL GEVL >>> procedure 1..1 SHALL >>>@ @classcode 1..1 SHALL CS SHALL PROC >>>@ @moodcode 1..1 SHALL CS SHALL RQO ReqProcCode >>>> code 1..1 SHALL CD ConceptDom ain ProedureCode Universal Service ID OBR-4 Amend the following section 9.8.1.1 text/content and @ID CDS Record The Request section narrative text block MAY include content blocks recording clinical decision support assessments of the request with respect to the indications, patient characteristics, and relevant guidelines. Each such text/content SHALL include an XML ID attribute that serves as the business name discriminator associated with an instantiation of the element. Even if only one content block is instantiated, the ID attribute shall be present. Each clinical decision support assessment record SHOULD have a corresponding structured entry. Add the following sections 9.8.1.2 entry/observation The Request section MAY include entries corresponding to the clinical decision support assessments in the narrative text block. 9.8.1.3 entry/observation/text/reference The observation entry SHALL include a text/reference element, whose value attribute SHALL begin with a '#' and SHALL point to its corresponding narrative content block. See Section 9.1.1.1. 9.8.1.4 entry/observation/methodcode The entry/observation/methodcode is the name of the Appropriate Use Criteria (AUC). Binding to the Value Set Concept Domain may be specific to the locale. Page 3

Note: In the United States, the Department of Health and Human Services will recognize or register sources of AUC clinical decision support rules for advanced imaging, and that registration number might be used as the methodcode. 9.8.1.5 entry/observation/author/assignedauthor The entry/observation/author/assignedauthor identifies the clinical decision support software application or service that evalutes a requested procedure against relevant Appropriate Use Criteria. This CDS is identified by the id and assignedauthoringdevice/softwarename elements. Notes: The CDS service is distinct from the AUC rules. An AUC rule might be implemented by multiple CDS services, and a CDS service might evaluate against multiple rules. In the United States, the Department of Health and Human Services will certify and register specific CDS software or services for advanced imaging procedures, and that registration number might be used as the id extension with DHHS as the assigning authority root. It is recommended that the assignedauthoringdevice/softwarename should include sufficient information to identify the specific instance of the CDS software, e.g., the name and version number of the software, and its execution location (e.g., as part of a local EMR instance, or as a remote web service). 9.8.1.6 entry/observation/participant/@typecode=ref The observation entry SHALL include a participant element with @typecode value REF identifying the the ordering physician for the requested procedure. This will typically be the same as the physician identified by the participant element with @typecode value REF in the header of the document (see Imaging Header). 9.8.1.7 entry/observation/actrelationship The entry/observation/actrelationship SHOULD reference the requested procedure code that was evaluated by the CDS service. Amend the example Figure 1: Request section example <section classcode="docsect" moodcode="evn"> <templateid root="1.2.840.10008.20.x2.x6" /> <id root="1.2.840.10213.2.62.7906994785528.114289506"/> <code code="55115-0" codesystemname="loinc" displayname="request" /> <title>request</title> <text>pta (Iliac Angioplasty) for treatment of symptomatic atherosclerotic disease in both iliac arteries. <content ID="CDS001">Procedure ordered by Pat Smith, MD, NPI:8740944987. Classified APPROPRIATE by RadCDS based on ACR Select criteria at 2015-07-21 10:52:31 CDT </content> </text> <entry> <observation classcode="obs" moodcode="evn" ID="CDS001-E"> <id root="1.2.840.90012.1097.9961.100" extension="20150721-16554"> <code code="76515-6" Page 4

codesystemname="loinc" displayname="requested Procedure is Appropriate" /> <text> <reference value="#cds001"> </text> <statuscode code="completed"/> <effectivetime value="20150721105231+0500"/> <value xsi:type="cd" code="la33-6" codesystemname="loinc" displayname="yes"/> <methodcode code="cds-003" codesystem="2.16.840.1.113883.19.166" codesystemname="us DHHS CDS" displayname="acr Select" /> <author> <time value= 20150721105231-0400" /> <assignedauthor> <id root="2.16.840.1.113883.19.169" extension="900104"> <assignedauthoringdevice> <softwarename>radcds</softwarename > </assignedauthoringdevice> </assignedauthor> </author> <participant typecode="ref"> <participantrole> <id root="2.16.840.1.113883.4.6" extension="8740944987" /> <playingentity classcode="psn"> <name>pat Smith, MD</name> </playingentity> </participantrole> </participant> </observation> </entry> </section> Page 5