[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [set] Groups - The Use of CCTS in HL7 CDA... (UseOfCCTSinCDA.ppt)uploaded
Dear David, Thank you for the comment and the contact points. I will prepare a a new SET TC Deliverable clearly describing the ideas that I have shortly presented in the slides and I will share it with all those interested. Allow me to note that Turkey is one of countries that have implemented HL7 CDA. Enclosed I have attached a paper: Kabak Y., Dogac A., Kose I., Akpinar N., Gurel M., Arslan Y., Ozer H., Yurt N., Ozcam A., Kirici S., Yuksel M., Sabur E. "The Use of HL7 CDA in the National Health Information System (NHIS) of Turkey", 9th International HL7 Interoperability Conference (IHIC) 2008, Crete, Greece, October 2008, pp. 49-55. Our experiences mainly stem from this work. Best regards, Asuman David RR Webber (XML) wrote: > Asuman, > > You should check with HL7. > > They had an RFP out earlier this year for Gap analysis - and I know > NIST have done registry work with them in the past on publishing > standards for clinical side of their world. > > I'd hate to be reinventing work they have already either done or > partially started and / or may want to contribute to! > > Thanks, DW > ========================================== > > Don Lloyd > Technical Publications Manager > Health Level Seven, Inc. > 3300 Washtenaw Ave. > Suite 227 > Ann Arbor, MI 48104 > 734-677-7777 > dlloyd@HL7.org <mailto:dlloyd@HL7.org> > > and > > Karen Van Hentenryck > Associate Executive Director > Health Level Seven, Inc. > 3300 Washtenaw Avenue, Suite 227 > Ann Arbor, MI 48104 > > Phone: 734-677-7777 > > > > > > -------- Original Message -------- > Subject: [set] Groups - The Use of CCTS in HL7 CDA... > (UseOfCCTSinCDA.ppt) uploaded > From: asuman@srdc.metu.edu.tr > Date: Wed, November 12, 2008 4:39 am > To: set@lists.oasis-open.org > > HL7 Clinical Document Architecture (CDA) schema instances are machine > processable because > they are XML documents with Structured body, Coded elements, using > HL7 Data > Types. > CDA Entry classes are created from RIM Act, Observation, > SubstanceAdministration, > Supply, Encounter, Procedure, ObservationMedia, Organizer, and > RegionOfInterest. > > However, HL7 CDA Documents can have any structure by nesting the > Sections > and Entries at any depth and in any way. Furthermore, there can be > data > elements > that are not defined for CDA but are necessary for local > implementations > such as > Vaccination, Discharge Method (referral, death or cured), Type of > Contagiousness, > etc. in local implementations. Additionally, there is a need for > expressing > > the CDA concepts in local languages for local implementations. > > In creating CDA documents at the Regional or National level, we > propose to start from UN/CEFACT CCTS: > - Define BCCs by using existing HL7 Data Types and Data Elements > - Define the missing data elements by constraining relevant RIM > classes > - Then define ACCs (minimum health data sets) by using BCCs > - Hence create a local (or national) data dictionary > - It may be much better if HL7 defines these constructs and the > countries > customize these according to their context > > Building a local or national common data dictionary consisting of data > elements (BCCs) and minimum health data sets (ACCs) will > - Clearly define the meaning of data elements > - Give their corresponding explanation in the local language > - Create the additional data elements needed locally from the > corresponding > RIM Classes > - Also note that defining minimum health data sets as Aggregate Core > Components will determine their structure and semantics > - All these will help with the interoperability of CDAs > > When these minimum health data sets (ACCs) are mapped to the CDA > Sections, there is not a unique way of doing this. Yet, SET TC > specifications can be used to provide the interoperability > of different CDA schemes. > > > -- Ms. Asuman Dogac* > > The document named The Use of CCTS in HL7 CDA... > (UseOfCCTSinCDA.ppt) has > been submitted by Ms. Asuman Dogac* to the OASIS Semantic Support for > Electronic Business Document Interoperability (SET) TC document > repository. > > Document Description: > HL7 Clinical Document Architecture (CDA) schema instances are machine > processable because > they are XML documents with Structured body, Coded elements, using > HL7 Data > Types. > CDA Entry classes are created from RIM Act, Observation, > SubstanceAdministration, > Supply, Encounter, Procedure, ObservationMedia, Organizer, and > RegionOfInterest. > > However, HL7 CDA Documents can have any structure by nesting the > Sections > and Entries at any depth and in any way. Furthermore, there can be > data > elements > that are not defined for CDA but are necessary for local > implementations > such as > Vaccination, Discharge Method (referral, death or cured), Type of > Contagiousness, > etc. in local implementations. Additionally, there is a need for > expressing > > the CDA concepts in local languages for local implementations. > > In creating CDA documents at the Regional or National level, we > propose to start from UN/CEFACT CCTS: > - Define BCCs by using existing HL7 Data Types and Data Elements > - Define the missing data elements by constraining relevant RIM > classes > - Then define ACCs (minimum health data sets) by using BCCs > - Hence create a local (or national) data dictionary > - It may be much better if HL7 defines these constructs and the > countries > customize these according to their context > > Building a local or national common data dictionary consisting of data > elements (BCCs) and minimum health data sets (ACCs) will > - Clearly define the meaning of data elements > - Give their corresponding explanation in the local language > - Create the additional data elements needed locally from the > corresponding > RIM Classes > - Also note that defining minimum health data sets as Aggregate Core > Components will determine their structure and semantics > - All these will help with the interoperability of CDAs > > When these minimum health data sets (ACCs) are mapped to the CDA > Sections, there is not a unique way of doing this. Yet, SET TC > specifications can be used to provide the interoperability > of different CDA schemas. > > > View Document Details: > http://www.oasis-open.org/committees/document.php?document_id=30019 > > Download Document: > http://www.oasis-open.org/committees/download.php/30019/UseOfCCTSinCDA.ppt > > > PLEASE NOTE: If the above links do not work for you, your email > application > may be breaking the link into two pieces. You may be able to copy > and paste > the entire link address into the address field of your web browser. > > -OASIS Open Administration > > --------------------------------------------------------------------- > To unsubscribe from this mail list, you must leave the OASIS TC that > generates this mail. Follow this link to all your TCs in OASIS at: > https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php -- ____________________________________________________________________________ Professor Asuman Dogac email: asuman@srdc.metu.edu.tr WWW: http://www.srdc.metu.edu.tr/~asuman/ Director Phone: +90 (312) 210 5598, or Software R&D Center +90 (312) 210 2076 Department of Computer Eng. Fax: +90 (312) 210 5572 Middle East Technical University +90 (312) 210 1259 06531 Ankara Turkey skype: adogac
FinalCDA.Turkey.IHIC08Formatted.pdf
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]