Query for Existing Data: Difference between revisions

From IHE Wiki
Jump to navigation Jump to search
Newer edit →
Kboone (talk | contribs)
4,700 edits
No edit summary
 
Kboone (talk | contribs)
4,700 edits
No edit summary
Line 1: Line 1:
=Introduction=
=Introduction=
''This is a draft of the Query for Dynamic Clinical Data Profile ({{{2}}}) supplement to the Patient Care Coordination Technical Framework.  This draft is a work in progress, not the official supplement or profile.''
''This is a draft of the Query for Dynamic Clinical Data Profile (QCD) supplement to the Patient Care Coordination Technical Framework.  This draft is a work in progress, not the official supplement or profile.''


__TOC__
__TOC__


==Profile Abstract==
==Profile Abstract==
The {{{1}}} Profile ({{{2}}}) {{{4|has a one paragraph description.}}}
The Query for Dynamic Clinical Data Profile (QCD) {{{4|has a one paragraph description.}}}


==Glossary==
==Glossary==
Line 16: Line 16:
=Volume I=
=Volume I=
<pre>Add the following bullet to the list of profiles</pre>
<pre>Add the following bullet to the list of profiles</pre>
* {{{1}}} - {{{3}}}
* Query for Dynamic Clinical Data - {{{3}}}


===Dependencies===
===Dependencies===
Line 26: Line 26:
!Purpose
!Purpose
|- style='background-color:#ffffff;' align='center'
|- style='background-color:#ffffff;' align='center'
|{{{1}}}
|Query for Dynamic Clinical Data
|
|
|
|
Line 33: Line 33:
|}
|}
==Profile Name==
==Profile Name==
The {{{1}}} Profile ({{{2}}}) {{{4|has a one paragraph description.}}}
The Query for Dynamic Clinical Data Profile (QCD) {{{4|has a one paragraph description.}}}


And then some more introductory text.
And then some more introductory text.
Line 49: Line 49:
The sharing or transmission of content or updates from one actor to the other is addressed by the use of appropriate IHE profiles described by section 3.7 Content Bindings with XDS, XDM and XDR found in the [[Frameworks#IHE_Patient_Care_Coordination_Technical_Framework|Patient Care Coordination Technical Framework]]
The sharing or transmission of content or updates from one actor to the other is addressed by the use of appropriate IHE profiles described by section 3.7 Content Bindings with XDS, XDM and XDR found in the [[Frameworks#IHE_Patient_Care_Coordination_Technical_Framework|Patient Care Coordination Technical Framework]]


[[image:cccc.png|frame|center|{{{1}}} Actor Diagram]]
[[image:cccc.png|frame|center|Query for Dynamic Clinical Data Actor Diagram]]


=== Options ===
=== Options ===
Line 57: Line 57:
!Option
!Option
!Section
!Section
|+{{{1}}} Options
|+Query for Dynamic Clinical Data Options
|- style='background-color:#ffffff;' align='center'
|- style='background-color:#ffffff;' align='center'
|Content Consumer
|Content Consumer
Line 79: Line 79:


=== Grouping ===
=== Grouping ===
==== Content Bindings with XDS, XDM and XDR====
It is expected that the transfers of care will occur in an environment where the physician offices and hospitals have a coordinated infrastructure that serves the information sharing needs of this community of care. Several mechanisms are supported by IHE profiles:
* A registry/repository-based infrastructure is defined by the IHE [[Cross Enterprise Document Sharing]] (XDS) and other IHE Integration Profiles such as patient identification (PIX & PDQ), and notification of availability of documents (NAV).
* A media-based infrastructure is defined by the IHE [[Cross Enterprise Document Media Interchange]] (XDM) profile.
* A reliable messaging-based infrastructure is defined by the IHE [[Cross Enterprise Document Reliable Interchange]] (XDR) profile.
* All of these infrastructures support Security and privacy through the use of the [[Consistent Time]] (CT) and [[Audit Trail and Node Authentication]] (ATNA) profiles.
For more details on these profiles, see the [[Frameworks#IHE_IT Infrastructure_Technical_Framework|IHE IT Infrastructure Technical Framework]].
Content profiles may impose additional requirements on the transactions used when grouped with actors from other IHE Profiles.
==== Cross Enterprise Document Sharing, Media Interchange and Reliable Messages ====
Actors from the ITI XDS, XDM and XDR profiles embody the [[Content Creator]] and [[Content Consumer]] sharing function of this profile. A [[Content Creator]] or [[Content Consumer]] must be grouped with appropriate actors from the XDS, XDM or XDR profiles, and the metadata sent in the document sharing or interchange messages has specific relationships to the content of the clinical document described in the content profile.
==== [[Notification of Document Availability]] (NAV) ====
A Document Source should provide the capability to issue a [[Send Notification]] Transaction per the ITI [[Notification of Document Availability]] (NAV) Integration Profile in order to notify one or
more [[Document Consumer]](s) of the availability of one or more documents for retrieval. One of the Acknowledgement Request options may be used to request from a Document Consumer that
an acknowledgement should be returned when it has received and processed the notification.
A Document Consumer should provide the capability to receive a [[Receive Notification]] Transaction per the NAV Integration Profile in order to be notified by Document Sources of the availability of one or more documents for retrieval. The [[Send Acknowledgement]] option may be used to issue a Send Acknowledgement to a [[Document Source]] that the notification was received and processed.
==== [[Document Digital Signature]] (DSG)====
When a [[Content Creator]] Actor needs to digitally sign a document in a submission set, it may support the Digital Signature (DSG) Content Profile as a [[Document Source]].
When a [[Content Consumer]] Actor needs to verify a Digital Signature, it may retrieve the digital signature document and may perform the verification against the signed document content.
=== Content Modules ===
Content modules describe the content of a payload found in an IHE transaction. Content profiles are transaction neutral. They do not have dependencies upon the transaction that they appear in.
==== Content Module 1 ====


=== Process Flow ===
=== Process Flow ===
[[Image:seq.jpg|frame|center|{{{1}}} Process Flow]]
[[Image:seq.jpg|frame|center|Query for Dynamic Clinical Data Process Flow]]


More text about process flow
More text about process flow
Line 118: Line 91:


=Volume II=
=Volume II=
==={{{1}}} Content===
===Query for Dynamic Clinical Data Content===
==== Standards ====
==== Standards ====
; [http://www.hl7.org/v3ballot/html/infrastructure/cda.htm CDAR2] : Clinical Document Architecture, Release 2, 2005 HL7
; [http://www.hl7.org/v3ballot/html/infrastructure/cda.htm CDAR2] : Clinical Document Architecture, Release 2, 2005 HL7
Line 125: Line 98:


; [http://www.snomed.org SNOMED] : Systemized Nomenclature for Medicine
; [http://www.snomed.org SNOMED] : Systemized Nomenclature for Medicine
==== Data Element Index ====
{| cellspacing=0 border=1 align='center'
!style='background-color:#cfcfcf' |Data Elements
!style='background-color:#cfcfcf' |Other Reference
!style='background-color:#cfcfcf' |LOINC Section or CDA Element
|+ {{{1}}} Data Elements
|-
|Data Element 1 || ||
|-
|Data Element 2 || ||
|-
|Data Element 3 || ||
|}
==== Document Specification ====
{| cellspacing=0 border=1 align='center'
! style='background-color:#cfcfcf'|Data Element
! style='background-color:#cfcfcf'|Opt
!  style='background-color:#cfcfcf'|Section
! style='background-color:#cfcfcf' |Template ID
|+ {{{1}}} Constraints
|-
|Data Element 1 ||R|| || 1.3.6.1.4.1.19376.1.5.3.1.3.X
|-
|Data Element 2 ||R2|| || 1.3.6.1.4.1.19376.1.5.3.1.3.Y
|-
|Data Element 3 ||O|| || 1.3.6.1.4.1.19376.1.5.3.1.3.Z
|}
==Section Template 1==
{| border=1 cellspacing=0
|-
!style='background-color:#cfcfcf;'|TemplateID
| colspan=2|1.3.6.1.4.1.19376.1.5.3.1.3.X
|-
!style='background-color:#cfcfcf;'|Parent Template
| colspan=2|1.3.6.1.4.1.19376.1.5.3.1.3.Y
|-
!style='background-color:#cfcfcf;'|General Description
|colspan=2|This section shall ...
|- style='background-color:#cfcfcf;'
!LOINC Code
!Opt
!Description
|-
|#####-#
|align='center'|R
|Description
|- style='background-color:#cfcfcf;'
!Entries
!Opt
!Description
|-
|1.3.6.1.4.1.19376.1.5.3.1.4.A
|align='center'|O
|Description
|- style='background-color:#cfcfcf;'
!Sub-sections
!Opt
!Description
|-
|1.3.6.1.4.1.19376.1.5.3.1.3.D
|align='center'|R
|Description
|}
==Header Template 1==
<pre>
<entry>An XML Example</entry>
</pre>
=== entry ===
Description of the entry element.
==Entry Template 1==
<pre>
<entry>An XML Example</entry>
</pre>
=== entry ===
Description of the entry element.


[[Category:Patient Care Coordination]]
[[Category:Patient Care Coordination]]
[[Category:Draft Profile Supplement]]
[[Category:Draft Profile Supplement]]

Revision as of 20:51, 6 February 2007

Introduction

This is a draft of the Query for Dynamic Clinical Data Profile (QCD) supplement to the Patient Care Coordination Technical Framework. This draft is a work in progress, not the official supplement or profile.

Profile Abstract

The Query for Dynamic Clinical Data Profile (QCD) has a one paragraph description.

Glossary

Term
Definition

Issue Log

Open Issues

  1. Issue
  2. Issue

Closed Issues

Volume I

Add the following bullet to the list of profiles
  • Query for Dynamic Clinical Data - {{{3}}}

Dependencies

Add the following row(s) to the list of dependencies
Integration Profile Dependency Dependency Type Purpose
Query for Dynamic Clinical Data

Profile Name

The Query for Dynamic Clinical Data Profile (QCD) has a one paragraph description.

And then some more introductory text.

Use Cases

Use Case Name 1

One or more paragraphs describing a clinical scenario.

Use Case Name 2

One or more paragraphs describing a clinical scenario.

Use Case Name 3

One or more paragraphs describing a clinical scenario.

Actors/Transaction

There are two actors in this profile, the Content Creator and the Content Consumer. Content is created by a Content Creator and is to be consumed by a Content Consumer. The sharing or transmission of content from one actor to the other is addressed by the appropriate use of IHE profiles described below, and is out of scope of this profile. A Document Source or a Portable Media Creator may embody the Content Creator Actor. A Document Consumer, a Document Recipient or a Portable Media Importer may embody the Content Consumer Actor. The sharing or transmission of content or updates from one actor to the other is addressed by the use of appropriate IHE profiles described by section 3.7 Content Bindings with XDS, XDM and XDR found in the Patient Care Coordination Technical Framework

Query for Dynamic Clinical Data Actor Diagram

Options

Actor Option Section
Query for Dynamic Clinical Data Options
Content Consumer View Option (1)

Document Import Option (1)
Section Import Option (1)
Discrete Data Import Option (1)

 PCC TF-1: 2.13.1

PCC TF-1: 2.13.2
PCC TF-1: 2.13.3
PCC TF-1: 2.13.4

Content Creator Referral Option (1)

Discharge Summary Option (1)

 PCC TF-1: 2.13.5

PCC TF-1: 2.13.6

Note 1: The Actor shall support at least one of these options.

Grouping

Process Flow

Query for Dynamic Clinical Data Process Flow

More text about process flow

Actor Definitions

Actor
Definition

Transaction Definitions

Transaction
Definition

Volume II

Query for Dynamic Clinical Data Content

Standards

CDAR2
Clinical Document Architecture, Release 2, 2005 HL7
CRS
Implementation Guide for CDA Release 2 – Level 1 and 2 – Care Record Summary (US realm), 2006, HL7.
CCD
ASTM/HL7 Continuity of Care Document (Draft)
SNOMED
Systemized Nomenclature for Medicine
Retrieved from "http://wiki.ihe.net/index.php?title=Query_for_Existing_Data&oldid=2660"