CDA Examples

Derek,

Can you post examples of how IHE would do the following

Results ….

[1] Here is a Chem 12

[2] Here is an update to that same chem12

[3] Here is a radiology report. (Prelim)

[4] Here is the final.

ADT ….

[5] Here is a registration

[6] Here is a name correction

[7] Here is a discharge

Larry Lemmon is developing sample V2 messages that support this.

I’d like to see what the corresponding CDA documents would be.

Thanks,

Mark

···

Mark Tucker

Systems Engineer

Regenstrief Institute

(317)423-5552

mtucker2@regenstrief.org

Confidentiality Notice: The contents of this message and any files transmitted with it may contain confidential and/or privileged information and are intended
solely for the use of the named addressee(s). Additionally, the information contained herein may have been disclosed to you from medical records with confidentiality protected by federal and state laws. Federal regulations and State laws prohibit you from
making further disclosure of such information without the specific written consent of the person to whom the information pertains or as otherwise permitted by such regulations. A general authorization for the release of medical or other information is not
sufficient for this purpose.

If you have received this message in error, please notify the sender by return e-mail and delete the original message. Any retention, disclosure, copying, distribution or use of this information by anyone other than the intended recipient is strictly prohibited

Hi Mark.

Thank you for thinking I’m clever enough to construct CDAs and XDS messages. :wink:

This feels like a technology “bake-off” and, as I’ve indicated previously, I’m not convinced that’s the right way to approach this decision. That said, a group that could readily document these technical comparisons is Mohawk. They are adept in and have developed (thru their various partnerships and engagements) working prototypes across the full range of message and content specifications (HL7v2, HL7v3, IHE, and even OpenEHR I think). I posted a link to work they did a couple of years ago on this topic; it was included in the minutes.

I still feel, quite strongly, that the choice of a stack of standards is an ecosystem decision that should be made by the senior OpenHIE leadership on behalf of all the communities.

Warmest regards,

Derek.

Derek Ritz, P.Eng., CPHIMS-CA

ecGroup Inc.

+1 (905) 515-0045

www.ecgroupinc.com

This communication is intended only for the party to whom it is addressed, and may contain information which is privileged or confidential. Any other delivery, distribution, copying or disclosure is strictly prohibited and is not a waiver of privilege or confidentiality. If you have received this telecommunication in error, please notify the sender immediately by return electronic mail and destroy the message and any attachments.

···

Le présent courriel et les documents qui y sont joints sont confidentiels et protégés et s’adressent exclusivement au destinataire mentionné ci-dessus. L’expéditeur ne renonce pas aux droits et privilèges qui s’y rapportent ni à leur caractère confidentiel. Toute prise de connaissance, diffusion, utilisation ou reproduction de ce message ou des documents qui y sont joints, ainsi que des renseignements que chacun contient, par une personne autre que le destinataire prévu est interdite. Si vous recevez ce courriel par erreur, veuillez le détruire immédiatement et m’en informer.

From: openhie-shr@googlegroups.com [mailto:openhie-shr@googlegroups.com] On Behalf Of Tucker, Mark
Sent: August 6, 2013 3:05 PM
To: Derek Ritz (ecGroup); openhie-shr
Subject: CDA Examples

Derek,

Can you post examples of how IHE would do the following

Results ….

[1] Here is a Chem 12

[2] Here is an update to that same chem12

[3] Here is a radiology report. (Prelim)

[4] Here is the final.

ADT ….

[5] Here is a registration

[6] Here is a name correction

[7] Here is a discharge

Larry Lemmon is developing sample V2 messages that support this.

I’d like to see what the corresponding CDA documents would be.

Thanks,

Mark

Mark Tucker

Systems Engineer

Regenstrief Institute

(317)423-5552

mtucker2@regenstrief.org

Confidentiality Notice: The contents of this message and any files transmitted with it may contain confidential and/or privileged information and are intended solely for the use of the named addressee(s). Additionally, the information contained herein may have been disclosed to you from medical records with confidentiality protected by federal and state laws. Federal regulations and State laws prohibit you from making further disclosure of such information without the specific written consent of the person to whom the information pertains or as otherwise permitted by such regulations. A general authorization for the release of medical or other information is not sufficient for this purpose.

If you have received this message in error, please notify the sender by return e-mail and delete the original message. Any retention, disclosure, copying, distribution or use of this information by anyone other than the intended recipient is strictly prohibited


You received this message because you are subscribed to the Google Groups “Shared Health Record (OpenHIE)” group.
To unsubscribe from this group and stop receiving emails from it, send an email to openhie-shr+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Hi Mark :slight_smile:

Comments below:

Derek,

Can you post examples of how IHE would do the following

Results ….

[1] Here is a Chem 12

[2] Here is an update to that same chem12

[3] Here is a radiology report. (Prelim)

[4] Here is the final.

All of these transactions would be supported in IHE through the XDS base profile. It presumes that all results come in the form of documents, which one can quibble about the extra heft that this brings about.

However, most people I’ve seen do XDS in the real world use a v2 message with prespecified reference terminologies (LOINC, etc), and wrap these messages an XDS envelope to make them “document-like”.

More specificity around labs is here:

http://wiki.ihe.net/index.php?title=Sharing_Laboratory_Reports

More specificity around radiology is here:

http://www.ihe.net/Technical_Framework/upload/IHE_RAD-TF_Suppl_XDSI_TI_2005-08-15.pdf

ADT ….

[5] Here is a registration

[6] Here is a name correction

[7] Here is a discharge

Larry Lemmon is developing sample V2 messages that support this.

I’d like to see what the corresponding CDA documents would be.

I’m under the impression that these would be PIX/PDQ queries:

http://wiki.ihe.net/index.php?title=Patient_Identifier_Cross_Referencing

http://wiki.ihe.net/index.php?title=Patient_Demographics_Query

These can also be “wrapped” v2 messages, from what I’ve seen in practice.

-Paul

···

On Tue, Aug 6, 2013 at 3:04 PM, Tucker, Mark mtucker2@regenstrief.org wrote:

Thanks for this Paul. Is it your feeling that IHE profiles (XDS with CDA, PIX and PDQ profiles) would provide us with what we need for OpenHIE?

In terms of PIX and PDQ, those are implemented either just plain profiled HL7v2 messages or as profiled HL7v3 messages.

Cheers,

Ryan

···

On Wed, Aug 7, 2013 at 7:32 PM, Paul Biondich pbiondic@regenstrief.org wrote:

Hi Mark :slight_smile:

Comments below:

On Tue, Aug 6, 2013 at 3:04 PM, Tucker, Mark mtucker2@regenstrief.org wrote:

Derek,

Can you post examples of how IHE would do the following

Results ….

[1] Here is a Chem 12

[2] Here is an update to that same chem12

[3] Here is a radiology report. (Prelim)

[4] Here is the final.

All of these transactions would be supported in IHE through the XDS base profile. It presumes that all results come in the form of documents, which one can quibble about the extra heft that this brings about.

However, most people I’ve seen do XDS in the real world use a v2 message with prespecified reference terminologies (LOINC, etc), and wrap these messages an XDS envelope to make them “document-like”.

More specificity around labs is here:

http://wiki.ihe.net/index.php?title=Sharing_Laboratory_Reports

More specificity around radiology is here:

http://www.ihe.net/Technical_Framework/upload/IHE_RAD-TF_Suppl_XDSI_TI_2005-08-15.pdf

ADT ….

[5] Here is a registration

[6] Here is a name correction

[7] Here is a discharge

Larry Lemmon is developing sample V2 messages that support this.

I’d like to see what the corresponding CDA documents would be.

I’m under the impression that these would be PIX/PDQ queries:

http://wiki.ihe.net/index.php?title=Patient_Identifier_Cross_Referencing

http://wiki.ihe.net/index.php?title=Patient_Demographics_Query

These can also be “wrapped” v2 messages, from what I’ve seen in practice.

-Paul

You received this message because you are subscribed to the Google Groups “Shared Health Record (OpenHIE)” group.

To unsubscribe from this group and stop receiving emails from it, send an email to openhie-shr+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.


Ryan Crichton

Software Developer, Jembi Health Systems | SOUTH AFRICA

Mobile: +27845829934 | Skype: ryan.graham.crichton
E-mail: ryan@jembi.org

Hi Ryan, two comments. One, I don’t have enough direct experience with using them to feel totally confident with them at this point. We need to poke heavily at them. But we should start poking. :slight_smile:

Two, I don’t think that those two profiles are sufficient alone.

···

On Wed, Aug 7, 2013 at 7:32 PM, Paul Biondich pbiondic@regenstrief.org wrote:

Hi Mark :slight_smile:

Comments below:

On Tue, Aug 6, 2013 at 3:04 PM, Tucker, Mark mtucker2@regenstrief.org wrote:

Derek,

Can you post examples of how IHE would do the following

Results ….

[1] Here is a Chem 12

[2] Here is an update to that same chem12

[3] Here is a radiology report. (Prelim)

[4] Here is the final.

All of these transactions would be supported in IHE through the XDS base profile. It presumes that all results come in the form of documents, which one can quibble about the extra heft that this brings about.

However, most people I’ve seen do XDS in the real world use a v2 message with prespecified reference terminologies (LOINC, etc), and wrap these messages an XDS envelope to make them “document-like”.

More specificity around labs is here:

http://wiki.ihe.net/index.php?title=Sharing_Laboratory_Reports

More specificity around radiology is here:

http://www.ihe.net/Technical_Framework/upload/IHE_RAD-TF_Suppl_XDSI_TI_2005-08-15.pdf

ADT ….

[5] Here is a registration

[6] Here is a name correction

[7] Here is a discharge

Larry Lemmon is developing sample V2 messages that support this.

I’d like to see what the corresponding CDA documents would be.

I’m under the impression that these would be PIX/PDQ queries:

http://wiki.ihe.net/index.php?title=Patient_Identifier_Cross_Referencing

http://wiki.ihe.net/index.php?title=Patient_Demographics_Query

These can also be “wrapped” v2 messages, from what I’ve seen in practice.

-Paul


You received this message because you are subscribed to the Google Groups “Shared Health Record (OpenHIE)” group.

To unsubscribe from this group and stop receiving emails from it, send an email to openhie-shr+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

Ryan Crichton

Software Developer, Jembi Health Systems | SOUTH AFRICA

Mobile: +27845829934 | Skype: ryan.graham.crichton

E-mail: ryan@jembi.org