HL7 pan-Canadian Standards Review call – CDA proposed changes

Thanks a lot Wendy for organizing the call

I would like to give an overview on Ontario’s rationale behind the proposed changes which we are planning to discuss in our next meeting :

For TEL.ALL, our use case is simple - we have a requirement to support phone numbers, email addresses and web addresses. Some of our consumers have information on provider's and organization's email and web addresses in the CDA documents they send to the repository.

For AD.FULL we have a requirement to support discrete address parts, e.g. street name, dwelling number, etc. - some of our consumers send documents with discrete information and expect us to keep it as is in the repository.

Looking forward to discuss the above in more details with community members.

Thank you to all those who participated on the call today.

Click here for updated spreadsheet with the decisions made on today's call in the right most column "HL7 pan-Canadian Standards Review call 2015-06-04". The participants agreed on the proposed process to use on discussing and advancing proposed changes to the pan-Canadian standards.

On the next call, we will continue our discussion on a variety of items such as the proposed changes to the Person Name, Address, and Telecommunication data types , as well as a constraint note on the informationRecipient/intendedRecipient. The intention for the continuing discussion is also indicated under the right most column "HL7 pan-Canadian Standards Review call 2015-06-04".

Stay tuned for logistic details for the next HL7 pan-Canadian Standards Review call.

This is a reminder regarding the HL7 Community call tomorrow to discuss and advance proposed changes to the pan-Canadian CDA Header.

Call details:
June 4, 2015
12-1 pm Eastern Time (UTC-4)

Webex: infoway-inforoute.webex.com/infoway-inforoute/j.php?MTID=m25e74eb87de4a1e9d1512c13057a9c8f

Teleconference information:
Call-in toll-free number: 1-8666260833 (Canada & US)
Conference Code: 163 110 6739
Show global numbers: www.tcconline.com/offSite/OffSiteController.jpf?cc=1631106739

Add call details to your calendar

You are encouraged to review the propose changes and comments prior to joining the call so that the value of the call will be maximized and outcomes are achieved.

From the list of proposed changes:
Technical corrections:

1. Incorrect code for author/@typeCode - change #8
2. Incorrect nullFlavor statements – change #1
3. Previous approved change applied incorrectly for ClinicalDocument/title – change #2
4. Incorrect value set OID for ActClassRoot (change #9)
5. Clarify wording – change #15

Proposed changes that require community input are:

1. Change cardinality for recordTarget/patientRole/patient/languageCommunication/LanguageCode – change #6
2. Change data types for Person Name, Address, and Telecommunication types from “basic” to “full”. A discussion has started on this set of proposed changes (#11-13).
3. Add a condition on informationRecipient/intendedRecipient that it has to be either a person or an organization – change #14
4. Regarding the terminology for inFulfillmentOf/order/code and documentationOf/serviceEvent/code (change #10), it requires constrain from ActCode, and implementer input to inform the scope of terminology to support the identified data elements.

Looking forward to your participation.

Wendy Huang
Standards SME
Canada Health Infoway

To determine next steps for the recent changes Ontario put forward on the pan-Canadian Clinical Document Architecture (CDA) Header, a call has been scheduled to discuss and hopefully reach consensus on the proposed changes.

Call details:
June 4, 2015
12-1 pm Eastern Time (UTC-4)

Webex: infoway-inforoute.webex.com/infoway-inforoute/j.php?MTID=m25e74eb87de4a1e9d1512c13057a9c8f

Teleconference information:
Call-in toll-free number: 1-8666260833 (Canada & US)
Conference Code: 163 110 6739
Show global numbers: www.tcconline.com/offSite/OffSiteController.jpf?cc=1631106739

Add call details to your calendar

You are encouraged to review the propose changes and comments prior to joining the call so that the value of the call will be maximized and outcomes are achieved.

From the list of proposed changes:
Technical corrections:

1. Incorrect code for author/@typeCode - change #8
2. Incorrect nullFlavor statements – change #1
3. Previous approved change applied incorrectly for ClinicalDocument/title – change #2
4. Incorrect value set OID for ActClassRoot (change #9)
5. Clarify wording – change #15

Proposed changes that require community input are:

1. Change cardinality for recordTarget/patientRole/patient/languageCommunication/LanguageCode – change #6
2. Change data types for Person Name, Address, and Telecommunication types from “basic” to “full”. A discussion has started on this set of proposed changes (#11-13).
3. Add a condition on informationRecipient/intendedRecipient that it has to be either a person or an organization – change #14
4. Regarding the terminology for inFulfillmentOf/order/code and documentationOf/serviceEvent/code (change #10), it requires constrain from ActCode, and implementer input to inform the scope of terminology to support the identified data elements.

Looking forward to your participation.

Best regards,
Wendy