https://wiki.hl7.org/w/api.phpHL7Wiki - User contributions [en]2024-03-28T13:15:57ZUser contributionsMediaWiki 1.33.0https://wiki.hl7.org/w/index.php?title=Implementation_Guides&diff=87782Implementation Guides2014-06-16T14:38:22Z<p>Charliemccay: /* other links */ removed broken link</p>
<hr />
<div>This page should provide an overview about existing or ongoing activities on Implementation Guides.<br />
Currently, there is an ongoing project within ICTC to collect information about implementation guides.<br />
HL7 Germany has provided a template which can be used as a template for writing those guides. However, it is informative and may provide information of what can be placed within such a guide.<br />
<br />
It should be noted, that IHE is doing a lot on integration profiles which are based on v2.x and V3/CDA. Some of them are known, others are not. However, it may make sense to collect this information in a central place as it may be unknown to some of us.<br />
<br />
If you have additional information pleaes feel free to add it to the list.<br />
<br />
==Version 2.x==<br />
<br />
===Implementation Guides (by country)===<br />
*USA<br />
**[http://www.cdc.gov/vaccines/programs/iis/stds/downloads/hl7-guide2010-508.pdf Immunization History messaging].<br />
*Germany<br />
**[[http://www.hl7.de Message Profiles]]<br />
<br />
===Implementation Guides (by organisation)===<br />
*IHE<br />
**IHE ITI<br />
**IHE Radiology<br />
**IHE Laboratory<br />
***[http://www.ihe.net/Technical_Framework/upload/LabTFVol1_v1_1_jul08_FT.pdf IHE Lab profile, volume 1], [http://www.ihe.net/Technical_Framework/upload/LabTFVol2_v1_2_feb27_FT.pdf IHE Lab profile, volume 2]. Typical IHE v2 message based profile.<br />
**...<br />
<br />
<br />
<br />
===Tools===<br />
*Editors/Validators<br />
**MWB (Message Workbench)<br />
*HAPI (HL7 API)<br />
*Message Maker (NIST)<br />
*DVTk (DICOM Validation Toolkit)<br />
<br />
==Version 3==<br />
<br />
===Implementation Guides (by country)===<br />
*USA<br />
**[http://www.fda.gov/oc/datacouncil/splr3_Implementation_Guidev1_1.pdf SPL Implemenation guide] This guide explains the standard based on examples<br />
*Germany<br />
**Data Types<br />
**Versichertenstammdaten<br />
**Order Entry Communication using Patient Care Transfer Requests<br />
**Diagnosis (ICD10 + ICD-O (TNM-classification))<br />
*The Netherlands<br />
**[http://www.sbv-ztest.nl/Images/Conformanceprofiel%20SBV-Z%20BSN%20Opvraag-Verificatie%20(4%2E0)_tcm17-2994.pdf Dutch National Person Registry]. v3 message implementation guide. (in Dutch)<br />
<br />
===Implementation Guides (by organisation)===<br />
*IHE<br />
**IHE ITI<br />
***[http://www.ihe.net/Technical_Framework/upload/IHE_ITI_TF_Suppl_PIX_PDQ_HL7v3_TI_2006_11_06.pdf IHE ITI MPI]. IHE profile for v3 messages.<br />
<br />
<br />
==HL7 Templates==<br />
*Patient Care SIG<br />
**score and assessment systems (in progress)<br />
<br />
Please see also the [[http://detailedclinicalmodels.org detailed clinical information models]] (DCM) website.<br />
<br />
==CDA==<br />
<br />
===Implementation Guides (by country)===<br />
*USA<br />
**CCD (Continuity of Care Document) Rel.1<br />
**CRS (Care Record Summary)<br />
**[[http://www.fda.gov/oc/datacouncil/splr3_Implementation_Guidev1_1.pdf SPL - This guide is designed for software developers]]<br />
**HAI (Healthcare associated infections)<br />
**HITSP<br />
***C32<br />
***C37<br />
***C48<br />
***C49<br />
**Consultation Notes<br />
**History and Physical<br />
**Operative Notes<br />
**Imaging Integration, Basic Imaging Reports<br />
*Canada<br />
**e-MS (electronic Mecial Summary)<br />
*UK<br />
*Germany<br />
**[[http://www.hl7.de/download/documents/cdar2-arztbrief/Leitfaden-VHitG-Arztbrief-v150.pdf VHitG-Arztbrief v1.50]] (German CDA discharge summary)<br />
**[[http://www.hl7.de/download/documents/cdar2-arztbrief/Addendum-Lab100.zip Addendum Laboratory]]<br />
**[[http://www.hl7.de/download/documents/cdar2-arztbrief/Addendum-Med-v100.pdf Addendum Medication]]<br />
**Addendum notifiable diseases (in progress)<br />
**DRV Reha-Enlassbrief<br />
**Reha-Kurzarztbrief<br />
**Nursing Summary (ePflegebericht)<br />
*South Korea<br />
**[http://www.hl7.de/iamcda2004/finalmat/day4/CDA_final_CDAconference_KHS.pdf CDA conference 2004]<br />
*Austria<br />
**[http://www.elga.gv.at ELGA] (currently in progress)<br />
*Switzerland<br />
**CDA-CH v1.1<br />
*France<br />
**[http://guepard.contingences.com/IMG/pdf/Guide_Implementation_Volet_Medical_CDA_Release_2_Niveau_3_v0-7.pdf French CRS CDA Body implementation Guide] (in French)<br />
*Finland<br />
**seamless Care and CDA<br />
**[https://www.kanta.fi/fi/hl7 Finnish (CDA) implementation guides]: CDA R2, V3, Medical Records, V2, CDA R (in Finnish)<br />
**[https://www.kanta.fi/en brief info about our national archive] (in English)<br />
*Japan<br />
**[http://www.hl7.jp/intro/std/HL7J-CDA-001.pdf Japanese Clinical Summary document] (in Japanese)<br />
<br />
===Implementation Guides (by organisation)===<br />
*IHE ITI<br />
**XDS-SD (CDA level 0)<br />
**XDS-MS<br />
**Emergency Department Referral<br />
**PHR Extract<br />
**Antepartum Care Summary<br />
**Functional Status Assessment<br />
*IHE PCC<br />
**CDA Templates<br />
*epSOS<br />
**Medical Summary<br />
**ePrescription<br />
<br />
===direct links by country===<br />
*Australia<br />
**[[http://e-health.standards.org.au/cat.asp?catid=16&area=pubs 45 implementation guides and handbooks]]<br />
{{TC Category}}<br />
*Turkey<br />
**[[http://www.ehealth-bg.org/images/Presentation_Bulgaria_1.pdf EHR]]<br />
*The Netherlands<br />
**[[http://www.ringholm.de/docs/00980_en.htm AORTA]]<br />
<br />
===Tools===<br />
*Editors<br />
**CDA-Editor<br />
*Validators<br />
**NIST<br />
**Alschuler Associates<br />
<br />
===other links===<br />
<!-- [[http://www.showmeyourcda.net www.showmeyourcda.net]] --> <!--broken link --></div>Charliemccayhttps://wiki.hl7.org/w/index.php?title=SHN_Patient_Summary_CDA_specificiations_in_Europe&diff=81195SHN Patient Summary CDA specificiations in Europe2013-12-17T13:20:55Z<p>Charliemccay: /* Table of Patient Summary Implementations */</p>
<hr />
<div>= Introduction = <br />
This page provides a table of CDA Patient Summary Projects in EU countries<br />
<br />
The initial contents were derived from systematic review of the reports from EU affiliates available from the notes from the last 2 Working Group Meetings.<br />
<br />
Next steps:<br />
* Strategy for fleshing out the list<br />
** email all HL7 EU chairs asking for information and/or to directly update the wiki<br />
** review EU project websites<br />
** email EU project contacts<br />
<br />
= Table of Patient Summary Implementations =<br />
<br />
{|class="wikitable"<br />
! Country<br />
! Project<br />
! Specification<br />
! Contact<br />
|-<br />
|[http://www.hl7.at/ Austria] <br />
|ELGA: National Health Record<br />
Various CDA implementation guides have been developed and balloted:<br />
* Common Implementation Guide (basis of all Austrian CDA-documents, Header Specification)<br />
* Discharge Letter (Physician)<br />
* Discharge Letter (Nursing)<br />
* Laboratory Report<br />
* Diagnostic Imaging Report<br />
* In preparation: Pathology Report, Microbiology Report<br />
A national Patient Summary is being discussed<br />
|http://www.elga.gv.at/index.php?id=28<br />
|http://www.elga.gv.at<br />
http://www.hl7.at<br />
|-<br />
|Bosnia and Herzegovina<br />
|<br />
|<br />
|<br />
|-<br />
|[http://www.hl7.hr/ Croatia]<br />
|<br />
|<br />
|<br />
|-<br />
|Czech Republic<br />
|In development, interest in cooperating with German and Austrian neighbours<br />
|<br />
|http://www.hl7.cz <br />
|-<br />
|Finland<br />
|Kanta Oral Health CDA specification in development<br />
CDA for ePrescribing in Finland<br />
|<br />
|http://www.hl7.fi <br />
|-<br />
|France<br />
|CDA is mandated for patient care coordination. XD-LAB has been chosen for lab reports. APSR is required for cancer case AP reports.<br />
|<br />
|<br />
|-<br />
|[http://www.hl7.de/ Germany]<br />
|eArztbrief<br />
|http://www.hl7.de/download/documents/cdar2-arztbrief/Leitfaden-VHitG-Arztbrief-v150.pdf<br />
|http://www.hl7.de<br />
|-<br />
| Greece<br />
|<br />
|<br />
|<br />
|-<br />
|Italy<br />
|CDA Implementation Guides<br />
* Lab report<br />
* Prescribing<br />
* Patient Summary<br />
* Header<br />
|http://www.hl7italia.it/node/34<br />
|http://www.hl7italia.it <br />
|-<br />
|Luxembourg<br />
|<br />
|<br />
|<br />
|-<br />
|Netherlands<br />
|NFU/Nictiz<br />
|<br />
|http://www.nictiz.nl<br />
|-<br />
|Norway<br />
|<br />
|<br />
|<br />
|-<br />
|Romania<br />
|<br />
|<br />
|<br />
|-<br />
|Sweden<br />
|<br />
|<br />
|<br />
|-<br />
|Spain<br />
|Various CDA implementation guides have been developed, available on HL7 Spain website.<br />
|http://www.hl7spain.org/guias-implementacion.html<br />
|http://www.hl7spain.org<br />
|-<br />
|Switzerland<br />
|CDA-CH<br />
* 2002: Swiss translations (and narrowing) of several HL7 V2 user defined tables<br />
* 2004: Implementation Guide: Patient Admin Interface HL7 V2.4<br />
* 2004: Z-Segment (ZSA) for PAM Interface, defines values for psychiatry<br />
* 2004: Z-Segment (ZGI) for PAM Interface, defines values for neotatology<br />
* 2011: CDA-CH II (V 1.2, de, fr, it, en), basis for Swiss CDA Templates<br />
* 2013: CDA-CH-LRTP Template for transplantation info (approval pending)<br />
* 2013: CDA-CH-EDES Implementation guide for emergency discharge report (approval pending)<br />
* 2013: CDA-CH-MSET Implementation guide for medical emergency data (approval pending)<br />
* 2013: CDA-? eImmunoDoc: Template for immunization data (in preparation)<br />
|<br />
<br />
|http://www.hl7.ch <br />
|-<br />
|Turkey<br />
|<br />
|<br />
|<br />
|-<br />
|UK<br />
|<br />
|<br />
|<br />
|}</div>Charliemccayhttps://wiki.hl7.org/w/index.php?title=HL7_in_Europe&diff=80538HL7 in Europe2013-11-26T11:41:40Z<p>Charliemccay: Created page with "This is a placeholder page to provide a focus for European topics in the HL7 wiki. It will include links to the European Office website, European projects that have a HL7 aspe..."</p>
<hr />
<div>This is a placeholder page to provide a focus for European topics in the HL7 wiki. <br />
<br />
It will include links to the European Office website, European projects that have a HL7 aspect, HL7 projects that have a European aspect - and other such topics of European interest.<br />
<br />
As a wiki page it is open to anyone to contribute content - and so to build up a resource for Europeans with an interest in HL7</div>Charliemccayhttps://wiki.hl7.org/w/index.php?title=SemanticHealthNet&diff=80537SemanticHealthNet2013-11-26T11:36:44Z<p>Charliemccay: </p>
<hr />
<div>__NOTOC__<br />
Mid migration to use the project template: Project Page Template - This template is for voluntary use, but provides guidance for consistent representation of wiki pages reporting project information<br />
<br />
<br />
Return to the HL7 wiki [[Main Page]], [http://www.hl7.org/about/hl7europeoffice.cfm HL7 EU Office], [[HL7 in Europe]] wiki page or [[International_Council|International Council]] wiki page''<br />
<br />
<!-- <br />
*list project co-sponsors and link to their WG [[Main_Page|wiki page]] or [http://www.hl7.org/Special/committees/index.cfm?ref=nav Work Group web pages]<br />
awaiting confirmation of sponsorship<br />
--><br />
<br />
==Project Information==<br />
<br />
<!--<br />
Link to [http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm Project Insight Searchable Database] Entry, which contains:<br />
*Brief description of project. <br />
*Name the project facilitators, (add contact info if desired)<br />
*Link to project scope statement. <br />
*Name the [http://www.hl7.org/listservice/index.cfm? project listserv] if a special one exists<br />
--><br />
The project scope statement is still in draft being reviewed by the EU Office Taskforce<br />
<br />
Further details about the project can be found at http://www.semantichealthnet.eu/ or by contacting Charlie McCay (charlie@ramseysystems.co.uk).<br />
<br />
The SemanticHealthNet project is focused on organisational and governance processes, and is not resourced to create deployment-ready standards - however if the project is able to work with others to progress materials thorugh ballot then that would be a great outcome. Please get in touch with Charlie McCay (charlie@ramseysystems.co.uk) if you are interested in taking any of the SemanticHealthNet deliverables further, or you think that there are other projects happening in HL7 that SemanticHealthNet should eb engaged in.<br />
<br />
SemanticHealthNet will develop a scalable and sustainable pan-European organisational and governance process for the semantic interoperability of clinical and biomedical knowledge, to help ensure that EHR systems are optimised for patient care, public health and clinical research across healthcare systems and institutions.<br />
<br />
Through a clinically-driven workplan, exemplified in cardiovascular medicine, SemanticHealthNet will capture the needs for evidence-based, patient-centred integrated care and for public health, encapsulating existing European consensus in the management of chronic heart failure and cardiovascular prevention. Experts in EHR architectures, clinical data structures, terminologies and ontology will combine, tailor and pilot their best-of-breed resources in response to the needs articulated by clinicians and public health physicians.<br />
<br />
These exemplars will be cross-referenced with other domains and stakeholder perspectives via Clinical and Industrial Advisory Boards and interactions with other projects in Topic 5.3. The project will generalise and formalise the methods and best practices in how to combine and adapt informatics resources to support semantic interoperability, and how these can be developed and supported at scale. Health authorities, clinical professionals, ministries, vendors, purchasers, insurers are involved to ensure the project approach and results are realistically adoptable and viable, building on the SemanticHEALTH and CALLIOPE roadmaps.<br />
<br />
A business model to justify strategic investments, including the opportunity costs for key stakeholders such as SDOs, industry, will be defined. This, and links with epSOS II and the eHealth Governance Initiative, will inform the shape of the Virtual Organisation that this Network will establish to sustain semantic interoperability developments and their adoption.<br />
<br />
The consortium comprises more than 40 internationally recognised experts, including from USA and Canada, ensuring a global impact.<br />
<br />
==Meeting Information==<br />
<!--<br />
*link to or list [http://www.hl7.org/concalls/index.cfm?action=home.welcome& project meeting schedule]<br />
*[http://www.hl7.org/special/Committees/claims/minutes.cfm link to minutes web page] or [[Meeting_Minutes_template|wiki minutes page]], or list project meeting agendas and minutes<br />
--><br />
*16th Oct will be discussed by EU Office taskforce<br />
<br />
==Status==<br />
<!--<br />
*If balloting, list ballot name/[http://www.hl7.org/ctl.cfm?action=ballots.home&ballot_cycle_id=523&ballot_voter_id=0 cycle]/[http://www.hl7.org/documentcenter/ballots/2011may/downloads/ISO_IDMP_SUBSTID11238_R1_N1_2011MAR.pdf link]<br />
*If in DSTU, link to [http://www.hl7.org/dstucomments/ DSTU comments page]<br />
*If in development, link to [http://gforge.hl7.org/gf/project/work in progress]<br />
*Some projects explicitly list objectives from scope statement and status for each<br />
--><br />
<br />
:20th Sept 2012 update: <br />
:Done:<br />
:A draft Project scope statement has been circulated to the HL7 European Taskforce for review.<br />
:A draft CDA instance for a Heart Failure Summary document has been created.<br />
:A draft requirements checklist<br />
:Next Steps:<br />
:get Project Scope Statement Approved <br />
:Create a Heart Failure Summary CDA IG based on the requirements gathered by the project<br />
:Improve project wiki page<br />
:Establish an online documents repository<br />
:Create a FHIR IG based on the Heart Failure Summary requirements<br />
<br />
==Issues/Hot Topics==<br />
*List issues or link to issues tracking repository ([[Template:NEW_V3_Publishing_Issue|wiki pages]] or [http://gforge.hl7.org/gf/project/ GForge])<br />
<br />
<br />
==Project Documents==<br />
=== Project Deliverables ===<br />
These are all documents that are internal to the project. HL7 is not directly responsible for any of the document that will be delivered to the European Union. That said, material in these deliverables will be included in the final project deliverables. All documents are available from Charlie McCay on request - they will be posted to suitable places on the HL7 website / wiki once these are arranged.<br />
====Completed Documents====<br />
* Heart Care CDA Example Instance<br />
* Presentation "Beyond Documents" looking at what else SHN needs to address beyond the specification of clinical documents<br />
====Work in progress====<br />
* Revised Heart Care CDA Example Instance<br />
* Project Scope Statement<br />
* HL7 SHN CDA Implementation Guide Development Process. This is a document looking at how CDA Implementation Guides should be developed in SHN, and what guidance for producing CDA implementation guides should be provided to/by the SHN Virtual Organisation.<br />
* Horizon Scan of CDA Patient Summaries used in Europe - see [[SHN Patient Summary CDA specificiations in Europe]]<br />
<br />
====Planned Documents====<br />
* HL7 SHN CDA Implementation guide for Heart Care Summary (based on epSOS tabular implementation guide style)<br />
* HL7 SHN ValueSet Definition Languages <br />
* HL7 SHN Guidelines formalisms options paper<br />
<br />
<!--<br />
*Link to working documents/[[Main_Page|wiki pages]]<br />
*Link to [http://gforge.hl7.org/gf/project/ project GForge]<br />
*Link to reference documentation on [http://gforge.hl7.org/gf/project/ GForge], HL7 Web site [http://www.hl7.org/special/Committees/claims/docs.cfm WG Documents/Presentations page], or external web pages<br />
<br />
--><br />
<br />
<noinclude>==Categorization== </noinclude><br />
[[Category:Active_Projects]]</div>Charliemccayhttps://wiki.hl7.org/w/index.php?title=SHN_Patient_Summary_CDA_specificiations_in_Europe&diff=78303SHN Patient Summary CDA specificiations in Europe2013-09-23T18:20:52Z<p>Charliemccay: /* Table of Patient Summary Implementations */</p>
<hr />
<div>= Introduction = <br />
This page provides a table of CDA Patient Summary Projects in EU countries<br />
<br />
The initial contents were derived from systematic review of the reports from EU affiliates available from the notes from the last 2 Working Group Meetings.<br />
<br />
Next steps:<br />
* Strategy for fleshing out the list<br />
** email all HL7 EU chairs asking for information and/or to directly update the wiki<br />
** review EU project websites<br />
** email EU project contacts<br />
<br />
= Table of Patient Summary Implementations =<br />
<br />
{|class="wikitable"<br />
! Country<br />
! Project<br />
! Specification<br />
! Contact<br />
|-<br />
|[http://www.hl7.at/ Austria] <br />
|ELGA: National Health Record<br />
Various CDA implementation guides have been developed and balloted:<br />
* Common Implementation Guide (basis of all Austrian CDA-documents, Header Specification)<br />
* Discharge Letter (Physician)<br />
* Discharge Letter (Nursing)<br />
* Laboratory Report<br />
* Diagnostic Imaging Report<br />
* In preparation: Pathology Report, Microbiology Report<br />
A national Patient Summary is being discussed<br />
|http://www.elga.gv.at/index.php?id=28<br />
|http://www.elga.gv.at<br />
http://www.hl7.at<br />
|-<br />
|Bosnia and Herzegovina<br />
|<br />
|<br />
|<br />
|-<br />
|[http://www.hl7.hr/ Croatia]<br />
|<br />
|<br />
|<br />
|-<br />
|Czech Republic<br />
|In development, interest in cooperating with German and Austrian neighbours<br />
|<br />
|http://www.hl7.cz <br />
|-<br />
|Finland<br />
|Kanta Oral Health CDA specification in development<br />
CDA for ePrescribing in Finland<br />
|<br />
|http://www.hl7.fi <br />
|-<br />
|France<br />
|CDA is mandated for patient care coordination. XD-LAB has been chosen for lab reports. APSR is required for cancer case AP reports.<br />
|<br />
|<br />
|-<br />
|[http://www.hl7.de/ Germany]<br />
|eArztbrief<br />
|http://www.hl7.de/download/documents/cdar2-arztbrief/Leitfaden-VHitG-Arztbrief-v150.pdf<br />
|http://www.hl7.de<br />
|-<br />
| Greece<br />
|<br />
|<br />
|<br />
|-<br />
|Italy<br />
|CDA Implementation Guides<br />
* Lab report<br />
* Prescribing<br />
* Patient Summary<br />
* Header<br />
|http://www.hl7italia.it/node/34<br />
|http://www.hl7italia.it <br />
|-<br />
|Luxembourg<br />
|<br />
|<br />
|<br />
|-<br />
|Netherlands<br />
|NFU/Nictiz<br />
|<br />
|http://www.nictiz.nl<br />
|-<br />
|Norway<br />
|<br />
|<br />
|<br />
|-<br />
|Romania<br />
|<br />
|<br />
|<br />
|-<br />
|Sweden<br />
|<br />
|<br />
|<br />
|-<br />
|Spain<br />
|Various CDA implementation guides have been developed, available on HL7 Spain website.<br />
|http://www.hl7spain.org/guias-implementacion.html<br />
|http://www.hl7spain.org<br />
|-<br />
|Switzerland<br />
|CDA-CH<br />
|<br />
|http://www.hl7.ch <br />
|-<br />
|Turkey<br />
|<br />
|<br />
|<br />
|-<br />
|UK<br />
|<br />
|<br />
|<br />
|}</div>Charliemccayhttps://wiki.hl7.org/w/index.php?title=SHN_Patient_Summary_CDA_specificiations_in_Europe&diff=78300SHN Patient Summary CDA specificiations in Europe2013-09-23T18:18:24Z<p>Charliemccay: </p>
<hr />
<div>= Introduction = <br />
This page provides a table of CDA Patient Summary Projects in EU countries<br />
<br />
The initial contents were derived from systematic review of the reports from EU affiliates available from the notes from the last 2 Working Group Meetings.<br />
<br />
Next steps:<br />
* Strategy for fleshing out the list<br />
** email all HL7 EU chairs asking for information and/or to directly update the wiki<br />
** review EU project websites<br />
** email EU project contacts<br />
<br />
= Table of Patient Summary Implementations =<br />
<br />
{|class="wikitable"<br />
! Country<br />
! Project<br />
! Specification<br />
! Contact<br />
|-<br />
|[http://www.hl7.at/ Austria] <br />
|ELGA: National Health Record<br />
Various CDA implementation guides have been developed and balloted:<br />
* Common Implementation Guide (basis of all Austrian CDA-documents, Header Specification)<br />
* Discharge Letter (Physician)<br />
* Discharge Letter (Nursing)<br />
* Laboratory Report<br />
* Diagnostic Imaging Report<br />
* In preparation: Pathology Report, Microbiology Report<br />
A national Patient Summary is being discussed<br />
|http://www.elga.gv.at/index.php?id=28<br />
|http://www.elga.gv.at<br />
http://www.hl7.at<br />
|-<br />
|Bosnia and Herzegovina<br />
|<br />
|<br />
|<br />
|-<br />
|[http://www.hl7.hr/ Croatia]<br />
|<br />
|<br />
|<br />
|-<br />
|Czech Republic<br />
|In development, interest in cooperating with German and Austrian neighbours<br />
|<br />
|http://www.hl7.cz <br />
|-<br />
|Finland<br />
|Kanta Oral Health CDA specification in development<br />
CDA for ePrescribing in Finland<br />
|<br />
|http://www.hl7.fi <br />
|-<br />
|France<br />
|<br />
|<br />
|<br />
|-<br />
|[http://www.hl7.de/ Germany]<br />
|eArztbrief<br />
|http://www.hl7.de/download/documents/cdar2-arztbrief/Leitfaden-VHitG-Arztbrief-v150.pdf<br />
|http://www.hl7.de<br />
|-<br />
| Greece<br />
|<br />
|<br />
|<br />
|-<br />
|Italy<br />
|CDA Implementation Guides<br />
* Lab report<br />
* Prescribing<br />
* Patient Summary<br />
* Header<br />
|http://www.hl7italia.it/node/34<br />
|http://www.hl7italia.it <br />
|-<br />
|Luxembourg<br />
|<br />
|<br />
|<br />
|-<br />
|Netherlands<br />
|NFU/Nictiz<br />
|<br />
|http://www.nictiz.nl<br />
|-<br />
|Norway<br />
|<br />
|<br />
|<br />
|-<br />
|Romania<br />
|<br />
|<br />
|<br />
|-<br />
|Sweden<br />
|<br />
|<br />
|<br />
|-<br />
|Spain<br />
|Various CDA implementation guides have been developed, available on HL7 Spain website.<br />
|http://www.hl7spain.org/guias-implementacion.html<br />
|http://www.hl7spain.org<br />
|-<br />
|Switzerland<br />
|CDA-CH<br />
|<br />
|http://www.hl7.ch <br />
|-<br />
|Turkey<br />
|<br />
|<br />
|<br />
|-<br />
|UK<br />
|<br />
|<br />
|<br />
|}</div>Charliemccayhttps://wiki.hl7.org/w/index.php?title=SHN_Patient_Summary_CDA_specificiations_in_Europe&diff=78160SHN Patient Summary CDA specificiations in Europe2013-09-21T19:50:33Z<p>Charliemccay: </p>
<hr />
<div>= Introduction = <br />
This page provides a table of CDA Patient Summary Projects in EU countries<br />
<br />
The initial contents were derived from systematic review of the reports from EU affiliates available from the notes from the last 2 Working Group Meetings.<br />
<br />
Next steps:<br />
* Strategy for fleshing out the list<br />
** email all HL7 EU chairs asking for information and/or to directly update the wiki<br />
** review EU project websites<br />
** email EU project contacts<br />
<br />
<br />
{|class="wikitable"<br />
! Country<br />
! Project<br />
! Specification<br />
! Contact<br />
|-<br />
|[http://www.hl7.at/ Austria] <br />
|ELGA<br />
|<br />
|http://www.initiative-elga.at<br />
|-<br />
|Bosnia and Herzegovina<br />
|<br />
|<br />
|<br />
|-<br />
|[http://www.hl7.hr/ Croatia]<br />
|<br />
|<br />
|<br />
|-<br />
|Czech Republic<br />
|In development, interest in cooperating with German and Austrian neighbours<br />
|<br />
|http://www.hl7.cz <br />
|-<br />
|Finland<br />
|Kanta Oral Health CDA specification in development<br />
CDA for ePrescribing in Finland<br />
|<br />
|http://www.hl7.fi <br />
|-<br />
|France<br />
|<br />
|<br />
|<br />
|-<br />
|[http://www.hl7.de/ Germany]<br />
|eArztbrief<br />
|http://www.hl7.de/download/documents/cdar2-arztbrief/Leitfaden-VHitG-Arztbrief-v150.pdf<br />
|http://www.hl7.de<br />
|-<br />
| Greece<br />
|<br />
|<br />
|<br />
|-<br />
|Italy<br />
|CDA Implementation Guides<br />
* Lab report<br />
* Prescribing<br />
* Patient Summary<br />
* Header<br />
|http://www.hl7italia.it/node/34<br />
|http://www.hl7italia.it <br />
|-<br />
|Luxembourg<br />
|<br />
|<br />
|<br />
|-<br />
|Netherlands<br />
|NFU/Nictiz<br />
|<br />
|http://www.nictiz.nl<br />
|-<br />
|Norway<br />
|<br />
|<br />
|<br />
|-<br />
|Romania<br />
|<br />
|<br />
|<br />
|-<br />
|Sweden<br />
|<br />
|<br />
|<br />
|-<br />
|Spain<br />
|Various CDA implementation guides have been developed, available on HL7 Spain website.<br />
|http://www.hl7spain.org/guias-implementacion.html<br />
|http://www.hl7spain.org<br />
|-<br />
|Switzerland<br />
|CDA-CH<br />
|<br />
|http://www.hl7.ch <br />
|-<br />
|Turkey<br />
|<br />
|<br />
|<br />
|-<br />
|UK<br />
|<br />
|<br />
|<br />
|}</div>Charliemccayhttps://wiki.hl7.org/w/index.php?title=Talk:SHN_Patient_Summary_CDA_specificiations_in_Europe&diff=78156Talk:SHN Patient Summary CDA specificiations in Europe2013-09-21T18:34:55Z<p>Charliemccay: Created page with "The information available in the Country reports from the HL7 website was not as useful as hoped for this purpose. Maybe something to look into."</p>
<hr />
<div>The information available in the Country reports from the HL7 website was not as useful as hoped for this purpose.<br />
Maybe something to look into.</div>Charliemccayhttps://wiki.hl7.org/w/index.php?title=SHN_Patient_Summary_CDA_specificiations_in_Europe&diff=78153SHN Patient Summary CDA specificiations in Europe2013-09-21T18:19:11Z<p>Charliemccay: </p>
<hr />
<div>= Introduction = <br />
This page provides a table of CDA Patient Summary Projects in EU countries<br />
<br />
The initial contents were derived from systematic review of the reports from EU affiliates available from the notes from the last 2 Working Group Meetings.<br />
<br />
Next steps:<br />
* Strategy for fleshing out the list<br />
** email all HL7 EU chairs asking for information and/or to directly update the wiki<br />
** review EU project websites<br />
** email EU project contacts<br />
<br />
<br />
{|class="wikitable"<br />
! Country<br />
! Project<br />
! Specification<br />
! Contact<br />
|-<br />
|Austria<br />
|ELGA<br />
|<br />
|http://www.initiative-elga.at<br />
|-<br />
|Germany<br />
|eArztbrief<br />
|http://www.hl7.de/download/documents/cdar2-arztbrief/Leitfaden-VHitG-Arztbrief-v150.pdf<br />
|http://www.hl7.de<br />
|-<br />
|Italy<br />
|CDA Implementation Guides<br />
* Lab report<br />
* Prescribing<br />
* Patient Summary<br />
* Header<br />
|http://www.hl7italia.it/node/34<br />
|http://www.hl7italia.it <br />
|-<br />
|Netherlands<br />
|NFU/Nictiz<br />
|<br />
|http://www.nictiz.nl<br />
|-<br />
|Switzerland<br />
|CDA-CH<br />
|<br />
|http://www.hl7.ch <br />
|-<br />
|Finland<br />
|Kanta Oral Health CDA specification in development<br />
CDA for ePrescribing in Finland<br />
|<br />
|http://www.hl7.fi <br />
|-<br />
|Czech Republic<br />
|In development, interest in cooperating with German and Austrian neighbours<br />
|<br />
|http://www.hl7.cz <br />
|-<br />
|Spain<br />
|Various CDA implementation guides have been developed, available on HL7 Spain website.<br />
|http://www.hl7spain.org/guias-implementacion.html<br />
|http://www.hl7spain.org<br />
|}</div>Charliemccayhttps://wiki.hl7.org/w/index.php?title=SHN_Patient_Summary_CDA_specificiations_in_Europe&diff=78152SHN Patient Summary CDA specificiations in Europe2013-09-21T18:06:43Z<p>Charliemccay: charliemccay</p>
<hr />
<div>= Introduction = <br />
This page provides a table of CDA Patient Summary Projects in EU countries<br />
<br />
The initial contents were derived from systematic review of the reports from EU affiliates available from the notes from the last 2 Working Group Meetings.<br />
<br />
Next steps:<br />
* Strategy for fleshing out the list<br />
** email all HL7 EU chairs asking for information and/or to directly update the wiki<br />
** review EU project websites<br />
** email EU project contacts<br />
<br />
<br />
{|class="wikitable"<br />
! Country<br />
! Project<br />
! Specification<br />
! Contact<br />
|-<br />
|Austria<br />
|ELGA<br />
|<br />
|http://www.initiative-elga.at<br />
|-<br />
|Germany<br />
|eArztbrief<br />
|http://www.hl7.de/download/documents/cdar2-arztbrief/Leitfaden-VHitG-Arztbrief-v150.pdf<br />
|http://www.hl7.de<br />
|-<br />
|Italy<br />
|CDA Implementation Guides<br />
* Lab report<br />
* Prescribing<br />
* Patient Summary<br />
* Header<br />
|http://www.hl7italia.it/node/34<br />
|http://www.hl7italia.it <br />
|-<br />
|Netherlands<br />
|NFU/Nictiz<br />
|<br />
|http://www.nictiz.nl<br />
|-<br />
|Switzerland<br />
|CDA-CH<br />
|<br />
|http://www.hl7.ch <br />
|-<br />
|Finland<br />
|Kanta Oral Health CDA specification in development<br />
CDA for ePrescribing in Finland<br />
|<br />
|http://www.hl7.fi <br />
|-<br />
|Czech Republic<br />
|In development, interest in cooperating with German and Austrian neighbours<br />
|<br />
|http://www.hl7.cz <br />
|-<br />
|Spain<br />
|Various CDA implementation guides have been developed, available on HL7 Spain website.<br />
|http://www.hl7spain.org/guias-implementacion.html<br />
|http://www.hl7spain.org<br />
|}<br />
<br />
|}</div>Charliemccayhttps://wiki.hl7.org/w/index.php?title=SemanticHealthNet&diff=78151SemanticHealthNet2013-09-21T16:30:52Z<p>Charliemccay: /* Work in progress */</p>
<hr />
<div>__NOTOC__<br />
Mid migration to use the project template: Project Page Template - This template is for voluntary use, but provides guidance for consistent representation of wiki pages reporting project information<br />
<br />
<br />
Return to [[Main Page]], [http://www.hl7.org/about/hl7europeoffice.cfm HL7 EU Office] or [[International_Council|International Council]] ''<br />
<br />
<!-- <br />
*list project co-sponsors and link to their WG [[Main_Page|wiki page]] or [http://www.hl7.org/Special/committees/index.cfm?ref=nav Work Group web pages]<br />
awaiting confirmation of sponsorship<br />
--><br />
<br />
==Project Information==<br />
<br />
<!--<br />
Link to [http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm Project Insight Searchable Database] Entry, which contains:<br />
*Brief description of project. <br />
*Name the project facilitators, (add contact info if desired)<br />
*Link to project scope statement. <br />
*Name the [http://www.hl7.org/listservice/index.cfm? project listserv] if a special one exists<br />
--><br />
The project scope statement is still in draft being reviewed by the EU Office Taskforce<br />
<br />
Further details about the project can be found at http://www.semantichealthnet.eu/ or by contacting Charlie McCay (charlie@ramseysystems.co.uk).<br />
<br />
The SemanticHealthNet project is focused on organisational and governance processes, and is not resourced to create deployment-ready standards - however if the project is able to work with others to progress materials thorugh ballot then that would be a great outcome. Please get in touch with Charlie McCay (charlie@ramseysystems.co.uk) if you are interested in taking any of the SemanticHealthNet deliverables further, or you think that there are other projects happening in HL7 that SemanticHealthNet should eb engaged in.<br />
<br />
SemanticHealthNet will develop a scalable and sustainable pan-European organisational and governance process for the semantic interoperability of clinical and biomedical knowledge, to help ensure that EHR systems are optimised for patient care, public health and clinical research across healthcare systems and institutions.<br />
<br />
Through a clinically-driven workplan, exemplified in cardiovascular medicine, SemanticHealthNet will capture the needs for evidence-based, patient-centred integrated care and for public health, encapsulating existing European consensus in the management of chronic heart failure and cardiovascular prevention. Experts in EHR architectures, clinical data structures, terminologies and ontology will combine, tailor and pilot their best-of-breed resources in response to the needs articulated by clinicians and public health physicians.<br />
<br />
These exemplars will be cross-referenced with other domains and stakeholder perspectives via Clinical and Industrial Advisory Boards and interactions with other projects in Topic 5.3. The project will generalise and formalise the methods and best practices in how to combine and adapt informatics resources to support semantic interoperability, and how these can be developed and supported at scale. Health authorities, clinical professionals, ministries, vendors, purchasers, insurers are involved to ensure the project approach and results are realistically adoptable and viable, building on the SemanticHEALTH and CALLIOPE roadmaps.<br />
<br />
A business model to justify strategic investments, including the opportunity costs for key stakeholders such as SDOs, industry, will be defined. This, and links with epSOS II and the eHealth Governance Initiative, will inform the shape of the Virtual Organisation that this Network will establish to sustain semantic interoperability developments and their adoption.<br />
<br />
The consortium comprises more than 40 internationally recognised experts, including from USA and Canada, ensuring a global impact.<br />
<br />
==Meeting Information==<br />
<!--<br />
*link to or list [http://www.hl7.org/concalls/index.cfm?action=home.welcome& project meeting schedule]<br />
*[http://www.hl7.org/special/Committees/claims/minutes.cfm link to minutes web page] or [[Meeting_Minutes_template|wiki minutes page]], or list project meeting agendas and minutes<br />
--><br />
*16th Oct will be discussed by EU Office taskforce<br />
<br />
==Status==<br />
<!--<br />
*If balloting, list ballot name/[http://www.hl7.org/ctl.cfm?action=ballots.home&ballot_cycle_id=523&ballot_voter_id=0 cycle]/[http://www.hl7.org/documentcenter/ballots/2011may/downloads/ISO_IDMP_SUBSTID11238_R1_N1_2011MAR.pdf link]<br />
*If in DSTU, link to [http://www.hl7.org/dstucomments/ DSTU comments page]<br />
*If in development, link to [http://gforge.hl7.org/gf/project/work in progress]<br />
*Some projects explicitly list objectives from scope statement and status for each<br />
--><br />
<br />
:20th Sept 2012 update: <br />
:Done:<br />
:A draft Project scope statement has been circulated to the HL7 European Taskforce for review.<br />
:A draft CDA instance for a Heart Failure Summary document has been created.<br />
:A draft requirements checklist<br />
:Next Steps:<br />
:get Project Scope Statement Approved <br />
:Create a Heart Failure Summary CDA IG based on the requirements gathered by the project<br />
:Improve project wiki page<br />
:Establish an online documents repository<br />
:Create a FHIR IG based on the Heart Failure Summary requirements<br />
<br />
==Issues/Hot Topics==<br />
*List issues or link to issues tracking repository ([[Template:NEW_V3_Publishing_Issue|wiki pages]] or [http://gforge.hl7.org/gf/project/ GForge])<br />
<br />
<br />
==Project Documents==<br />
=== Project Deliverables ===<br />
These are all documents that are internal to the project. HL7 is not directly responsible for any of the document that will be delivered to the European Union. That said, material in these deliverables will be included in the final project deliverables. All documents are available from Charlie McCay on request - they will be posted to suitable places on the HL7 website / wiki once these are arranged.<br />
====Completed Documents====<br />
* Heart Care CDA Example Instance<br />
* Presentation "Beyond Documents" looking at what else SHN needs to address beyond the specification of clinical documents<br />
====Work in progress====<br />
* Revised Heart Care CDA Example Instance<br />
* Project Scope Statement<br />
* HL7 SHN CDA Implementation Guide Development Process. This is a document looking at how CDA Implementation Guides should be developed in SHN, and what guidance for producing CDA implementation guides should be provided to/by the SHN Virtual Organisation.<br />
* Horizon Scan of CDA Patient Summaries used in Europe - see [[SHN Patient Summary CDA specificiations in Europe]]<br />
<br />
====Planned Documents====<br />
* HL7 SHN CDA Implementation guide for Heart Care Summary (based on epSOS tabular implementation guide style)<br />
* HL7 SHN ValueSet Definition Languages <br />
* HL7 SHN Guidelines formalisms options paper<br />
<br />
<!--<br />
*Link to working documents/[[Main_Page|wiki pages]]<br />
*Link to [http://gforge.hl7.org/gf/project/ project GForge]<br />
*Link to reference documentation on [http://gforge.hl7.org/gf/project/ GForge], HL7 Web site [http://www.hl7.org/special/Committees/claims/docs.cfm WG Documents/Presentations page], or external web pages<br />
<br />
--><br />
<br />
<noinclude>==Categorization== </noinclude><br />
[[Category:Active_Projects]]</div>Charliemccayhttps://wiki.hl7.org/w/index.php?title=HL7_International_Foundation&diff=70987HL7 International Foundation2013-02-21T17:09:26Z<p>Charliemccay: </p>
<hr />
<div>The HL7 European Office is formally called "The HL7 International Foundation".<br />
<br />
*[http://www.hl7.org/about/hl7europeoffice.cfm www.hl7.org/about/hl7europeoffice.cfm]<br />
*[http://www.hl7.eu/ www.hl7.eu]<br />
<br />
The HL7 International Foundation co-ordinates HL7 engagement with Europe-wide organisations. <br />
<br />
It sponsors the [[SemanticHealthNet]] project</div>Charliemccayhttps://wiki.hl7.org/w/index.php?title=HL7_International_Foundation&diff=70980HL7 International Foundation2013-02-21T15:25:36Z<p>Charliemccay: </p>
<hr />
<div>The HL7 European Office is formally called "The HL7 International Foundation".<br />
<br />
*[http://www.hl7.org/about/hl7europeoffice.cfm www.hl7.org/about/hl7europeoffice.cfm]<br />
*[http://www.hl7.eu/ www.hl7.eu]</div>Charliemccayhttps://wiki.hl7.org/w/index.php?title=HL7_International_Foundation&diff=70979HL7 International Foundation2013-02-21T15:23:53Z<p>Charliemccay: Created page with "The HL7 European Office is formally called "The HL7 International Foundation". *[http://www.hl7.org/about/hl7europeoffice.cfm] *[http://www.hl7.eu/]"</p>
<hr />
<div>The HL7 European Office is formally called "The HL7 International Foundation".<br />
<br />
*[http://www.hl7.org/about/hl7europeoffice.cfm]<br />
*[http://www.hl7.eu/]</div>Charliemccayhttps://wiki.hl7.org/w/index.php?title=International_Council&diff=70977International Council2013-02-21T14:55:18Z<p>Charliemccay: /* Links */ Added a page for the International Foundation</p>
<hr />
<div>[[Image:DailyPlanet.gif|180px|right|thumb|Connecting the world]]<br />
This group supports the HL7 mission to create and promote its standards by helping to assure that the needs, issues and other input of all HL7 International Affiliates are recognized and effectively acted upon by the HL7 organization.<br />
==Making a global contribution==<br />
The International Council provides a forum for HL7 Affiliates and other interested HL7 members to communicate and exchange views as well as discuss issues regarding the international development, adoption, application and implementation of the HL7 standard.<br />
There are several ways to get involved with the international HL7 effort and get your ideas and opinions heard:<br />
*The International Council holds a full day meeting at every HL7 Working Group Meeting - usually on the Sunday before the main meeting begins. This is an open meeting, and all affiliate representatives and other interested HL7 members are invited to attend and contribute.<br />
*There is an International Council list server, which is open to all for discussion and sharing of ideas.<br />
*Once a year, the International Council organises the [[IHIC|International HL7 Interoperability Conference]], which provides a forum for HL7 users from around the world to come together and share their experiences. <br />
<br />
==Links==<br />
*[[International Mentoring Group|International Mentoring Committee]] (IMC)<br />
*[http://www.hl7.org/special/committees/international/index.cfm The HL7.org International Council web page]: Contact information for co-chairs and affiliate representatives - Mission/Charter statements - List server subscription - Affiliate agreements - Meeting minutes and other documentation<br />
*The [[HL7 International Foundation]] - The HL7 Office in Europe<br />
<br />
==Related==<br />
*[[SDO collaboration status]] lists the standards currently being worked on in collaboration with ISO and other SDOs<br />
*[[Report on the Strategic Initiative to the International Council]] (September 2006), part of the [[Strategic Initiative]].<br />
*The [[Realm]]-concept<br />
*[[HL7 Mission]]<br />
*[[international dialin advice for HL7 conference calls]]</div>Charliemccayhttps://wiki.hl7.org/w/index.php?title=SemanticHealthNet&diff=66631SemanticHealthNet2012-10-05T11:12:41Z<p>Charliemccay: /* Project Deliverables */</p>
<hr />
<div>__NOTOC__<br />
Mid migration to use the project template: Project Page Template - This template is for voluntary use, but provides guidance for consistent representation of wiki pages reporting project information<br />
<br />
<br />
Return to [[Main Page]], [http://www.hl7.org/about/hl7europeoffice.cfm HL7 EU Office] or [[International_Council|International Council]] ''<br />
<br />
<!-- <br />
*list project co-sponsors and link to their WG [[Main_Page|wiki page]] or [http://www.hl7.org/Special/committees/index.cfm?ref=nav Work Group web pages]<br />
awaiting confirmation of sponsorship<br />
--><br />
<br />
==Project Information==<br />
<br />
<!--<br />
Link to [http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm Project Insight Searchable Database] Entry, which contains:<br />
*Brief description of project. <br />
*Name the project facilitators, (add contact info if desired)<br />
*Link to project scope statement. <br />
*Name the [http://www.hl7.org/listservice/index.cfm? project listserv] if a special one exists<br />
--><br />
The project scope statement is still in draft being reviewed by the EU Office Taskforce<br />
<br />
Further details about the project can be found at http://www.semantichealthnet.eu/ or by contacting Charlie McCay (charlie@ramseysystems.co.uk).<br />
<br />
The SemanticHealthNet project is focused on organisational and governance processes, and is not resourced to create deployment-ready standards - however if the project is able to work with others to progress materials thorugh ballot then that would be a great outcome. Please get in touch with Charlie McCay (charlie@ramseysystems.co.uk) if you are interested in taking any of the SemanticHealthNet deliverables further, or you think that there are other projects happening in HL7 that SemanticHealthNet should eb engaged in.<br />
<br />
SemanticHealthNet will develop a scalable and sustainable pan-European organisational and governance process for the semantic interoperability of clinical and biomedical knowledge, to help ensure that EHR systems are optimised for patient care, public health and clinical research across healthcare systems and institutions.<br />
<br />
Through a clinically-driven workplan, exemplified in cardiovascular medicine, SemanticHealthNet will capture the needs for evidence-based, patient-centred integrated care and for public health, encapsulating existing European consensus in the management of chronic heart failure and cardiovascular prevention. Experts in EHR architectures, clinical data structures, terminologies and ontology will combine, tailor and pilot their best-of-breed resources in response to the needs articulated by clinicians and public health physicians.<br />
<br />
These exemplars will be cross-referenced with other domains and stakeholder perspectives via Clinical and Industrial Advisory Boards and interactions with other projects in Topic 5.3. The project will generalise and formalise the methods and best practices in how to combine and adapt informatics resources to support semantic interoperability, and how these can be developed and supported at scale. Health authorities, clinical professionals, ministries, vendors, purchasers, insurers are involved to ensure the project approach and results are realistically adoptable and viable, building on the SemanticHEALTH and CALLIOPE roadmaps.<br />
<br />
A business model to justify strategic investments, including the opportunity costs for key stakeholders such as SDOs, industry, will be defined. This, and links with epSOS II and the eHealth Governance Initiative, will inform the shape of the Virtual Organisation that this Network will establish to sustain semantic interoperability developments and their adoption.<br />
<br />
The consortium comprises more than 40 internationally recognised experts, including from USA and Canada, ensuring a global impact.<br />
<br />
==Meeting Information==<br />
<!--<br />
*link to or list [http://www.hl7.org/concalls/index.cfm?action=home.welcome& project meeting schedule]<br />
*[http://www.hl7.org/special/Committees/claims/minutes.cfm link to minutes web page] or [[Meeting_Minutes_template|wiki minutes page]], or list project meeting agendas and minutes<br />
--><br />
*16th Oct will be discussed by EU Office taskforce<br />
<br />
==Status==<br />
<!--<br />
*If balloting, list ballot name/[http://www.hl7.org/ctl.cfm?action=ballots.home&ballot_cycle_id=523&ballot_voter_id=0 cycle]/[http://www.hl7.org/documentcenter/ballots/2011may/downloads/ISO_IDMP_SUBSTID11238_R1_N1_2011MAR.pdf link]<br />
*If in DSTU, link to [http://www.hl7.org/dstucomments/ DSTU comments page]<br />
*If in development, link to [http://gforge.hl7.org/gf/project/work in progress]<br />
*Some projects explicitly list objectives from scope statement and status for each<br />
--><br />
<br />
:20th Sept 2012 update: <br />
:Done:<br />
:A draft Project scope statement has been circulated to the HL7 European Taskforce for review.<br />
:A draft CDA instance for a Heart Failure Summary document has been created.<br />
:A draft requirements checklist<br />
:Next Steps:<br />
:get Project Scope Statement Approved <br />
:Create a Heart Failure Summary CDA IG based on the requirements gathered by the project<br />
:Improve project wiki page<br />
:Establish an online documents repository<br />
:Create a FHIR IG based on the Heart Failure Summary requirements<br />
<br />
==Issues/Hot Topics==<br />
*List issues or link to issues tracking repository ([[Template:NEW_V3_Publishing_Issue|wiki pages]] or [http://gforge.hl7.org/gf/project/ GForge])<br />
<br />
<br />
==Project Documents==<br />
=== Project Deliverables ===<br />
These are all documents that are internal to the project. HL7 is not directly responsible for any of the document that will be delivered to the European Union. That said, material in these deliverables will be included in the final project deliverables. All documents are available from Charlie McCay on request - they will be posted to suitable places on the HL7 website / wiki once these are arranged.<br />
====Completed Documents====<br />
* Heart Care CDA Example Instance<br />
* Presentation "Beyond Documents" looking at what else SHN needs to address beyond the specification of clinical documents<br />
====Work in progress====<br />
* Revised Heart Care CDA Example Instance<br />
* Project Scope Statement<br />
* HL7 SHN CDA Implementation Guide Development Process. This is a document looking at how CDA Implementation Guides should be developed in SHN, and what guidance for producing CDA implementation guides should be provided to/by the SHN Virtual Organisation.<br />
<br />
====Planned Documents====<br />
* HL7 SHN CDA Implementation guide for Heart Care Summary (based on epSOS tabular implementation guide style)<br />
* HL7 SHN ValueSet Definition Languages <br />
* HL7 SHN Guidelines formalisms options paper<br />
<br />
<!--<br />
*Link to working documents/[[Main_Page|wiki pages]]<br />
*Link to [http://gforge.hl7.org/gf/project/ project GForge]<br />
*Link to reference documentation on [http://gforge.hl7.org/gf/project/ GForge], HL7 Web site [http://www.hl7.org/special/Committees/claims/docs.cfm WG Documents/Presentations page], or external web pages<br />
<br />
--><br />
<br />
<noinclude>==Categorization== </noinclude><br />
[[Category:Active_Projects]]</div>Charliemccayhttps://wiki.hl7.org/w/index.php?title=SemanticHealthNet&diff=66630SemanticHealthNet2012-10-05T11:11:10Z<p>Charliemccay: /* Project Documents */</p>
<hr />
<div>__NOTOC__<br />
Mid migration to use the project template: Project Page Template - This template is for voluntary use, but provides guidance for consistent representation of wiki pages reporting project information<br />
<br />
<br />
Return to [[Main Page]], [http://www.hl7.org/about/hl7europeoffice.cfm HL7 EU Office] or [[International_Council|International Council]] ''<br />
<br />
<!-- <br />
*list project co-sponsors and link to their WG [[Main_Page|wiki page]] or [http://www.hl7.org/Special/committees/index.cfm?ref=nav Work Group web pages]<br />
awaiting confirmation of sponsorship<br />
--><br />
<br />
==Project Information==<br />
<br />
<!--<br />
Link to [http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm Project Insight Searchable Database] Entry, which contains:<br />
*Brief description of project. <br />
*Name the project facilitators, (add contact info if desired)<br />
*Link to project scope statement. <br />
*Name the [http://www.hl7.org/listservice/index.cfm? project listserv] if a special one exists<br />
--><br />
The project scope statement is still in draft being reviewed by the EU Office Taskforce<br />
<br />
Further details about the project can be found at http://www.semantichealthnet.eu/ or by contacting Charlie McCay (charlie@ramseysystems.co.uk).<br />
<br />
The SemanticHealthNet project is focused on organisational and governance processes, and is not resourced to create deployment-ready standards - however if the project is able to work with others to progress materials thorugh ballot then that would be a great outcome. Please get in touch with Charlie McCay (charlie@ramseysystems.co.uk) if you are interested in taking any of the SemanticHealthNet deliverables further, or you think that there are other projects happening in HL7 that SemanticHealthNet should eb engaged in.<br />
<br />
SemanticHealthNet will develop a scalable and sustainable pan-European organisational and governance process for the semantic interoperability of clinical and biomedical knowledge, to help ensure that EHR systems are optimised for patient care, public health and clinical research across healthcare systems and institutions.<br />
<br />
Through a clinically-driven workplan, exemplified in cardiovascular medicine, SemanticHealthNet will capture the needs for evidence-based, patient-centred integrated care and for public health, encapsulating existing European consensus in the management of chronic heart failure and cardiovascular prevention. Experts in EHR architectures, clinical data structures, terminologies and ontology will combine, tailor and pilot their best-of-breed resources in response to the needs articulated by clinicians and public health physicians.<br />
<br />
These exemplars will be cross-referenced with other domains and stakeholder perspectives via Clinical and Industrial Advisory Boards and interactions with other projects in Topic 5.3. The project will generalise and formalise the methods and best practices in how to combine and adapt informatics resources to support semantic interoperability, and how these can be developed and supported at scale. Health authorities, clinical professionals, ministries, vendors, purchasers, insurers are involved to ensure the project approach and results are realistically adoptable and viable, building on the SemanticHEALTH and CALLIOPE roadmaps.<br />
<br />
A business model to justify strategic investments, including the opportunity costs for key stakeholders such as SDOs, industry, will be defined. This, and links with epSOS II and the eHealth Governance Initiative, will inform the shape of the Virtual Organisation that this Network will establish to sustain semantic interoperability developments and their adoption.<br />
<br />
The consortium comprises more than 40 internationally recognised experts, including from USA and Canada, ensuring a global impact.<br />
<br />
==Meeting Information==<br />
<!--<br />
*link to or list [http://www.hl7.org/concalls/index.cfm?action=home.welcome& project meeting schedule]<br />
*[http://www.hl7.org/special/Committees/claims/minutes.cfm link to minutes web page] or [[Meeting_Minutes_template|wiki minutes page]], or list project meeting agendas and minutes<br />
--><br />
*16th Oct will be discussed by EU Office taskforce<br />
<br />
==Status==<br />
<!--<br />
*If balloting, list ballot name/[http://www.hl7.org/ctl.cfm?action=ballots.home&ballot_cycle_id=523&ballot_voter_id=0 cycle]/[http://www.hl7.org/documentcenter/ballots/2011may/downloads/ISO_IDMP_SUBSTID11238_R1_N1_2011MAR.pdf link]<br />
*If in DSTU, link to [http://www.hl7.org/dstucomments/ DSTU comments page]<br />
*If in development, link to [http://gforge.hl7.org/gf/project/work in progress]<br />
*Some projects explicitly list objectives from scope statement and status for each<br />
--><br />
<br />
:20th Sept 2012 update: <br />
:Done:<br />
:A draft Project scope statement has been circulated to the HL7 European Taskforce for review.<br />
:A draft CDA instance for a Heart Failure Summary document has been created.<br />
:A draft requirements checklist<br />
:Next Steps:<br />
:get Project Scope Statement Approved <br />
:Create a Heart Failure Summary CDA IG based on the requirements gathered by the project<br />
:Improve project wiki page<br />
:Establish an online documents repository<br />
:Create a FHIR IG based on the Heart Failure Summary requirements<br />
<br />
==Issues/Hot Topics==<br />
*List issues or link to issues tracking repository ([[Template:NEW_V3_Publishing_Issue|wiki pages]] or [http://gforge.hl7.org/gf/project/ GForge])<br />
<br />
<br />
==Project Documents==<br />
=== Project Deliverables ===<br />
These are all documents that are internal to the project. HL7 is not directly responsible for any of the document that will be delivered to the European Union. That said, material in these deliverables will be included in the final project deliverables.<br />
====Completed Documents====<br />
* Heart Care CDA Example Instance<br />
* Presentation "Beyond Documents" looking at what else SHN needs to address beyond the specification of clinical documents<br />
====Work in progress====<br />
* Revised Heart Care CDA Example Instance<br />
* Project Scope Statement<br />
* HL7 SHN CDA Implementation Guide Development Process. This is a document looking at how CDA Implementation Guides should be developed in SHN, and what guidance for producing CDA implementation guides should be provided to/by the SHN Virtual Organisation.<br />
<br />
====Planned Documents====<br />
* HL7 SHN CDA Implementation guide for Heart Care Summary (based on epSOS tabular implementation guide style)<br />
* HL7 SHN ValueSet Definition Languages <br />
* HL7 SHN Guidelines formalisms options paper<br />
<br />
<!--<br />
*Link to working documents/[[Main_Page|wiki pages]]<br />
*Link to [http://gforge.hl7.org/gf/project/ project GForge]<br />
*Link to reference documentation on [http://gforge.hl7.org/gf/project/ GForge], HL7 Web site [http://www.hl7.org/special/Committees/claims/docs.cfm WG Documents/Presentations page], or external web pages<br />
<br />
--><br />
<br />
<noinclude>==Categorization== </noinclude><br />
[[Category:Active_Projects]]</div>Charliemccayhttps://wiki.hl7.org/w/index.php?title=SemanticHealthNet&diff=66096SemanticHealthNet2012-09-21T10:39:08Z<p>Charliemccay: </p>
<hr />
<div>__NOTOC__<br />
Mid migration to use the project template: Project Page Template - This template is for voluntary use, but provides guidance for consistent representation of wiki pages reporting project information<br />
<br />
<br />
Return to [[Main Page]], [http://www.hl7.org/about/hl7europeoffice.cfm HL7 EU Office] or [[International_Council|International Council]] ''<br />
<br />
<!-- <br />
*list project co-sponsors and link to their WG [[Main_Page|wiki page]] or [http://www.hl7.org/Special/committees/index.cfm?ref=nav Work Group web pages]<br />
awaiting confirmation of sponsorship<br />
--><br />
<br />
==Project Information==<br />
<br />
<!--<br />
Link to [http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm Project Insight Searchable Database] Entry, which contains:<br />
*Brief description of project. <br />
*Name the project facilitators, (add contact info if desired)<br />
*Link to project scope statement. <br />
*Name the [http://www.hl7.org/listservice/index.cfm? project listserv] if a special one exists<br />
--><br />
The project scope statement is still in draft being reviewed by the EU Office Taskforce<br />
<br />
Further details about the project can be found at http://www.semantichealthnet.eu/ or by contacting Charlie McCay (charlie@ramseysystems.co.uk).<br />
<br />
The SemanticHealthNet project is focused on organisational and governance processes, and is not resourced to create deployment-ready standards - however if the project is able to work with others to progress materials thorugh ballot then that would be a great outcome. Please get in touch with Charlie McCay (charlie@ramseysystems.co.uk) if you are interested in taking any of the SemanticHealthNet deliverables further, or you think that there are other projects happening in HL7 that SemanticHealthNet should eb engaged in.<br />
<br />
SemanticHealthNet will develop a scalable and sustainable pan-European organisational and governance process for the semantic interoperability of clinical and biomedical knowledge, to help ensure that EHR systems are optimised for patient care, public health and clinical research across healthcare systems and institutions.<br />
<br />
Through a clinically-driven workplan, exemplified in cardiovascular medicine, SemanticHealthNet will capture the needs for evidence-based, patient-centred integrated care and for public health, encapsulating existing European consensus in the management of chronic heart failure and cardiovascular prevention. Experts in EHR architectures, clinical data structures, terminologies and ontology will combine, tailor and pilot their best-of-breed resources in response to the needs articulated by clinicians and public health physicians.<br />
<br />
These exemplars will be cross-referenced with other domains and stakeholder perspectives via Clinical and Industrial Advisory Boards and interactions with other projects in Topic 5.3. The project will generalise and formalise the methods and best practices in how to combine and adapt informatics resources to support semantic interoperability, and how these can be developed and supported at scale. Health authorities, clinical professionals, ministries, vendors, purchasers, insurers are involved to ensure the project approach and results are realistically adoptable and viable, building on the SemanticHEALTH and CALLIOPE roadmaps.<br />
<br />
A business model to justify strategic investments, including the opportunity costs for key stakeholders such as SDOs, industry, will be defined. This, and links with epSOS II and the eHealth Governance Initiative, will inform the shape of the Virtual Organisation that this Network will establish to sustain semantic interoperability developments and their adoption.<br />
<br />
The consortium comprises more than 40 internationally recognised experts, including from USA and Canada, ensuring a global impact.<br />
<br />
==Meeting Information==<br />
<!--<br />
*link to or list [http://www.hl7.org/concalls/index.cfm?action=home.welcome& project meeting schedule]<br />
*[http://www.hl7.org/special/Committees/claims/minutes.cfm link to minutes web page] or [[Meeting_Minutes_template|wiki minutes page]], or list project meeting agendas and minutes<br />
--><br />
*16th Oct will be discussed by EU Office taskforce<br />
<br />
==Status==<br />
<!--<br />
*If balloting, list ballot name/[http://www.hl7.org/ctl.cfm?action=ballots.home&ballot_cycle_id=523&ballot_voter_id=0 cycle]/[http://www.hl7.org/documentcenter/ballots/2011may/downloads/ISO_IDMP_SUBSTID11238_R1_N1_2011MAR.pdf link]<br />
*If in DSTU, link to [http://www.hl7.org/dstucomments/ DSTU comments page]<br />
*If in development, link to [http://gforge.hl7.org/gf/project/work in progress]<br />
*Some projects explicitly list objectives from scope statement and status for each<br />
--><br />
<br />
:20th Sept 2012 update: <br />
:Done:<br />
:A draft Project scope statement has been circulated to the HL7 European Taskforce for review.<br />
:A draft CDA instance for a Heart Failure Summary document has been created.<br />
:A draft requirements checklist<br />
:Next Steps:<br />
:get Project Scope Statement Approved <br />
:Create a Heart Failure Summary CDA IG based on the requirements gathered by the project<br />
:Improve project wiki page<br />
:Establish an online documents repository<br />
:Create a FHIR IG based on the Heart Failure Summary requirements<br />
<br />
==Issues/Hot Topics==<br />
*List issues or link to issues tracking repository ([[Template:NEW_V3_Publishing_Issue|wiki pages]] or [http://gforge.hl7.org/gf/project/ GForge])<br />
<br />
<br />
==Project Documents==<br />
<!--<br />
*Link to working documents/[[Main_Page|wiki pages]]<br />
*Link to [http://gforge.hl7.org/gf/project/ project GForge]<br />
*Link to reference documentation on [http://gforge.hl7.org/gf/project/ GForge], HL7 Web site [http://www.hl7.org/special/Committees/claims/docs.cfm WG Documents/Presentations page], or external web pages<br />
<br />
--><br />
<br />
<noinclude>==Categorization== </noinclude><br />
[[Category:Active_Projects]]</div>Charliemccayhttps://wiki.hl7.org/w/index.php?title=SemanticHealthNet&diff=66095SemanticHealthNet2012-09-21T10:31:31Z<p>Charliemccay: </p>
<hr />
<div>__NOTOC__<br />
Mid migration to use the project template: Project Page Template - This template is for voluntary use, but provides guidance for consistent representation of wiki pages reporting project information<br />
<br />
<br />
Return to [[Main Page]], [http://www.hl7.org/about/hl7europeoffice.cfm HL7 EU Office] or [[International_Council|International Council]] ''<br />
<br />
# *list project co-sponsors and link to their WG [[Main_Page|wiki page]] or [http://www.hl7.org/Special/committees/index.cfm?ref=nav Work Group web pages]<br />
# awaiting confirmation of sponsorship<br />
<br />
==Project Information==<br />
<br />
# Link to [http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm Project Insight Searchable Database] Entry, which contains:<br />
# *Brief description of project. <br />
# *Name the project facilitators, (add contact info if desired)<br />
# *Link to project scope statement. <br />
# *Name the [http://www.hl7.org/listservice/index.cfm? project listserv] if a special one exists<br />
The project scope statement is still in draft being reviewed by the EU Office Taskforce<br />
<br />
Further details about the project can be found at http://www.semantichealthnet.eu/ or by contacting Charlie McCay (charlie@ramseysystems.co.uk).<br />
<br />
The SemanticHealthNet project is focused on organisational and governance processes, and is not resourced to create deployment-ready standards - however if the project is able to work with others to progress materials thorugh ballot then that would be a great outcome. Please get in touch with Charlie McCay (charlie@ramseysystems.co.uk) if you are interested in taking any of the SemanticHealthNet deliverables further, or you think that there are other projects happening in HL7 that SemanticHealthNet should eb engaged in.<br />
<br />
SemanticHealthNet will develop a scalable and sustainable pan-European organisational and governance process for the semantic interoperability of clinical and biomedical knowledge, to help ensure that EHR systems are optimised for patient care, public health and clinical research across healthcare systems and institutions.<br />
<br />
Through a clinically-driven workplan, exemplified in cardiovascular medicine, SemanticHealthNet will capture the needs for evidence-based, patient-centred integrated care and for public health, encapsulating existing European consensus in the management of chronic heart failure and cardiovascular prevention. Experts in EHR architectures, clinical data structures, terminologies and ontology will combine, tailor and pilot their best-of-breed resources in response to the needs articulated by clinicians and public health physicians.<br />
<br />
These exemplars will be cross-referenced with other domains and stakeholder perspectives via Clinical and Industrial Advisory Boards and interactions with other projects in Topic 5.3. The project will generalise and formalise the methods and best practices in how to combine and adapt informatics resources to support semantic interoperability, and how these can be developed and supported at scale. Health authorities, clinical professionals, ministries, vendors, purchasers, insurers are involved to ensure the project approach and results are realistically adoptable and viable, building on the SemanticHEALTH and CALLIOPE roadmaps.<br />
<br />
A business model to justify strategic investments, including the opportunity costs for key stakeholders such as SDOs, industry, will be defined. This, and links with epSOS II and the eHealth Governance Initiative, will inform the shape of the Virtual Organisation that this Network will establish to sustain semantic interoperability developments and their adoption.<br />
<br />
The consortium comprises more than 40 internationally recognised experts, including from USA and Canada, ensuring a global impact.<br />
<br />
==Meeting Information==<br />
*link to or list [http://www.hl7.org/concalls/index.cfm?action=home.welcome& project meeting schedule]<br />
*[http://www.hl7.org/special/Committees/claims/minutes.cfm link to minutes web page] or [[Meeting_Minutes_template|wiki minutes page]], or list project meeting agendas and minutes<br />
<br />
*16th Oct will be discussed by EU Office taskforce<br />
<br />
==Status==<br />
*If balloting, list ballot name/[http://www.hl7.org/ctl.cfm?action=ballots.home&ballot_cycle_id=523&ballot_voter_id=0 cycle]/[http://www.hl7.org/documentcenter/ballots/2011may/downloads/ISO_IDMP_SUBSTID11238_R1_N1_2011MAR.pdf link]<br />
*If in DSTU, link to [http://www.hl7.org/dstucomments/ DSTU comments page]<br />
*If in development, link to [http://gforge.hl7.org/gf/project/work in progress]<br />
*Some projects explicitly list objectives from scope statement and status for each<br />
<br />
20th Sept 2012 update: <br />
:Done:<br />
:A draft Project scope statement has been circulated to the HL7 European Taskforce for review.<br />
:A draft CDA instance for a Heart Failure Summary document has been created.<br />
:A draft requirements checklist<br />
:Next Steps:<br />
:Create a Heart Failure Summary CDA IG based on the requirements gathered by the project<br />
:Improve project wiki page<br />
:Create a FHIR IG based on the Heart Failure Summary requirements<br />
<br />
==Issues/Hot Topics==<br />
*List issues or link to issues tracking repository ([[Template:NEW_V3_Publishing_Issue|wiki pages]] or [http://gforge.hl7.org/gf/project/ GForge])<br />
<br />
<br />
==Project Documents==<br />
*Link to working documents/[[Main_Page|wiki pages]]<br />
*Link to [http://gforge.hl7.org/gf/project/ project GForge]<br />
*Link to reference documentation on [http://gforge.hl7.org/gf/project/ GForge], HL7 Web site [http://www.hl7.org/special/Committees/claims/docs.cfm WG Documents/Presentations page], or external web pages<br />
<br />
<br />
<noinclude>==Categorization== </noinclude><br />
To include your Project Page in a category listing, just include a statement like <nowiki>[[Category:Active_Projects]]</nowiki><br />
[[Category:StyleGuides]]</div>Charliemccayhttps://wiki.hl7.org/w/index.php?title=SemanticHealthNet&diff=66094SemanticHealthNet2012-09-21T10:21:27Z<p>Charliemccay: </p>
<hr />
<div>__NOTOC__<br />
Mid migration to use the project template: Project Page Template - This template is for voluntary use, but provides guidance for consistent representation of wiki pages reporting project information<br />
<br />
Return to [[Main Page]] - ''include link to return to [http://www.hl7.org/Special/committees/index.cfm?ref=nav Work Group main page] or [[Main_Page|wiki page]] who sponsored the project''<br />
*list project co-sponsors and link to their WG [[Main_Page|wiki page]] or [http://www.hl7.org/Special/committees/index.cfm?ref=nav Work Group web pages]<br />
<br />
==Project Information==<br />
<br />
Link to [http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm Project Insight Searchable Database] Entry, which contains:<br />
*Brief description of project. <br />
*Name the project facilitators, (add contact info if desired)<br />
*Link to project scope statement. <br />
*Name the [http://www.hl7.org/listservice/index.cfm? project listserv] if a special one exists<br />
*This is still in draft being reviewed by the EU Office Taskforce<br />
<br />
Further details about the project can be found at http://www.semantichealthnet.eu/ or by contacting Charlie McCay (charlie@ramseysystems.co.uk).<br />
<br />
The SemanticHealthNet project is focused on organisational and governance processes, and is not resourced to create deployment-ready standards - however if the project is able to work with others to progress materials thorugh ballot then that would be a great outcome. Please get in touch with Charlie McCay (charlie@ramseysystems.co.uk) if you are interested in taking any of the SemanticHealthNet deliverables further, or you think that there are other projects happening in HL7 that SemanticHealthNet should eb engaged in.<br />
<br />
SemanticHealthNet will develop a scalable and sustainable pan-European organisational and governance process for the semantic interoperability of clinical and biomedical knowledge, to help ensure that EHR systems are optimised for patient care, public health and clinical research across healthcare systems and institutions.<br />
<br />
Through a clinically-driven workplan, exemplified in cardiovascular medicine, SemanticHealthNet will capture the needs for evidence-based, patient-centred integrated care and for public health, encapsulating existing European consensus in the management of chronic heart failure and cardiovascular prevention. Experts in EHR architectures, clinical data structures, terminologies and ontology will combine, tailor and pilot their best-of-breed resources in response to the needs articulated by clinicians and public health physicians.<br />
<br />
These exemplars will be cross-referenced with other domains and stakeholder perspectives via Clinical and Industrial Advisory Boards and interactions with other projects in Topic 5.3. The project will generalise and formalise the methods and best practices in how to combine and adapt informatics resources to support semantic interoperability, and how these can be developed and supported at scale. Health authorities, clinical professionals, ministries, vendors, purchasers, insurers are involved to ensure the project approach and results are realistically adoptable and viable, building on the SemanticHEALTH and CALLIOPE roadmaps.<br />
<br />
A business model to justify strategic investments, including the opportunity costs for key stakeholders such as SDOs, industry, will be defined. This, and links with epSOS II and the eHealth Governance Initiative, will inform the shape of the Virtual Organisation that this Network will establish to sustain semantic interoperability developments and their adoption.<br />
<br />
The consortium comprises more than 40 internationally recognised experts, including from USA and Canada, ensuring a global impact.<br />
<br />
==Meeting Information==<br />
*link to or list [http://www.hl7.org/concalls/index.cfm?action=home.welcome& project meeting schedule]<br />
*[http://www.hl7.org/special/Committees/claims/minutes.cfm link to minutes web page] or [[Meeting_Minutes_template|wiki minutes page]], or list project meeting agendas and minutes<br />
<br />
*16th Oct will be discussed by EU Office taskforce<br />
<br />
==Status==<br />
*If balloting, list ballot name/[http://www.hl7.org/ctl.cfm?action=ballots.home&ballot_cycle_id=523&ballot_voter_id=0 cycle]/[http://www.hl7.org/documentcenter/ballots/2011may/downloads/ISO_IDMP_SUBSTID11238_R1_N1_2011MAR.pdf link]<br />
*If in DSTU, link to [http://www.hl7.org/dstucomments/ DSTU comments page]<br />
*If in development, link to [http://gforge.hl7.org/gf/project/work in progress]<br />
*Some projects explicitly list objectives from scope statement and status for each<br />
<br />
20th Sept 2012 update: <br />
:Done:<br />
:A draft Project scope statement has been circulated to the HL7 European Taskforce for review.<br />
:A draft CDA instance for a Heart Failure Summary document has been created.<br />
:A draft requirements checklist<br />
:Next Steps:<br />
:Create a Heart Failure Summary CDA IG based on the requirements gathered by the project<br />
:Improve project wiki page<br />
:Create a FHIR IG based on the Heart Failure Summary requirements<br />
<br />
==Issues/Hot Topics==<br />
*List issues or link to issues tracking repository ([[Template:NEW_V3_Publishing_Issue|wiki pages]] or [http://gforge.hl7.org/gf/project/ GForge])<br />
<br />
<br />
==Project Documents==<br />
*Link to working documents/[[Main_Page|wiki pages]]<br />
*Link to [http://gforge.hl7.org/gf/project/ project GForge]<br />
*Link to reference documentation on [http://gforge.hl7.org/gf/project/ GForge], HL7 Web site [http://www.hl7.org/special/Committees/claims/docs.cfm WG Documents/Presentations page], or external web pages<br />
<br />
<br />
<noinclude>==Categorization== </noinclude><br />
To include your Project Page in a category listing, just include a statement like <nowiki>[[Category:Active_Projects]]</nowiki><br />
[[Category:StyleGuides]]</div>Charliemccayhttps://wiki.hl7.org/w/index.php?title=SemanticHealthNet&diff=66076SemanticHealthNet2012-09-20T12:15:34Z<p>Charliemccay: start to use project template</p>
<hr />
<div>__NOTOC__<br />
Mid migration to use the project template: Project Page Template - This template is for voluntary use, but provides guidance for consistent representation of wiki pages reporting project information<br />
<br />
Return to [[Main Page]] - ''include link to return to [http://www.hl7.org/Special/committees/index.cfm?ref=nav Work Group main page] or [[Main_Page|wiki page]] who sponsored the project''<br />
*list project co-sponsors and link to their WG [[Main_Page|wiki page]] or [http://www.hl7.org/Special/committees/index.cfm?ref=nav Work Group web pages]<br />
<br />
==Project Information==<br />
<br />
Link to [http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm Project Insight Searchable Database] Entry, which contains:<br />
*Brief description of project. <br />
*Name the project facilitators, (add contact info if desired)<br />
*Link to project scope statement. <br />
*Name the [http://www.hl7.org/listservice/index.cfm? project listserv] if a special one exists<br />
*This is still in draft being reviewed by the EU Office Taskforce<br />
<br />
Further details about the project can be found at http://www.semantichealthnet.eu/ or by contacting Charlie McCay (charlie@ramseysystems.co.uk).<br />
<br />
The SemanticHealthNet project is focused on organisational and governance processes, and is not resourced to create deployment-ready standards - however if the project is able to work with others to progress materials thorugh ballot then that would be a great outcome. Please get in touch with Charlie McCay (charlie@ramseysystems.co.uk) if you are interested in taking any of the SemanticHealthNet deliverables further, or you think that there are other projects happening in HL7 that SemanticHealthNet should eb engaged in.<br />
<br />
SemanticHealthNet will develop a scalable and sustainable pan-European organisational and governance process for the semantic interoperability of clinical and biomedical knowledge, to help ensure that EHR systems are optimised for patient care, public health and clinical research across healthcare systems and institutions.<br />
<br />
Through a clinically-driven workplan, exemplified in cardiovascular medicine, SemanticHealthNet will capture the needs for evidence-based, patient-centred integrated care and for public health, encapsulating existing European consensus in the management of chronic heart failure and cardiovascular prevention. Experts in EHR architectures, clinical data structures, terminologies and ontology will combine, tailor and pilot their best-of-breed resources in response to the needs articulated by clinicians and public health physicians.<br />
<br />
These exemplars will be cross-referenced with other domains and stakeholder perspectives via Clinical and Industrial Advisory Boards and interactions with other projects in Topic 5.3. The project will generalise and formalise the methods and best practices in how to combine and adapt informatics resources to support semantic interoperability, and how these can be developed and supported at scale. Health authorities, clinical professionals, ministries, vendors, purchasers, insurers are involved to ensure the project approach and results are realistically adoptable and viable, building on the SemanticHEALTH and CALLIOPE roadmaps.<br />
<br />
A business model to justify strategic investments, including the opportunity costs for key stakeholders such as SDOs, industry, will be defined. This, and links with epSOS II and the eHealth Governance Initiative, will inform the shape of the Virtual Organisation that this Network will establish to sustain semantic interoperability developments and their adoption.<br />
<br />
The consortium comprises more than 40 internationally recognised experts, including from USA and Canada, ensuring a global impact.<br />
<br />
==Meeting Information==<br />
*link to or list [http://www.hl7.org/concalls/index.cfm?action=home.welcome& project meeting schedule]<br />
*[http://www.hl7.org/special/Committees/claims/minutes.cfm link to minutes web page] or [[Meeting_Minutes_template|wiki minutes page]], or list project meeting agendas and minutes<br />
<br />
*16th Oct will be discussed by EU Office taskforce<br />
<br />
==Status==<br />
*If balloting, list ballot name/[http://www.hl7.org/ctl.cfm?action=ballots.home&ballot_cycle_id=523&ballot_voter_id=0 cycle]/[http://www.hl7.org/documentcenter/ballots/2011may/downloads/ISO_IDMP_SUBSTID11238_R1_N1_2011MAR.pdf link]<br />
*If in DSTU, link to [http://www.hl7.org/dstucomments/ DSTU comments page]<br />
*If in development, link to [http://gforge.hl7.org/gf/project/work in progress]<br />
*Some projects explicitly list objectives from scope statement and status for each<br />
<br />
20th Sept 2012 update: <br />
Done:<br />
A draft Project scope statement has been circulated to the HL7 European Taskforce for review.<br />
A draft CDA instance for a Heart Failure Summary document has been created.<br />
Next Steps:<br />
Create a Heart Failure Summary CDA IG based on the requirements gathered by the project<br />
Improve project wiki page<br />
Create a FHIR IG based on the Heart Failure Summary requirements<br />
<br />
==Issues/Hot Topics==<br />
*List issues or link to issues tracking repository ([[Template:NEW_V3_Publishing_Issue|wiki pages]] or [http://gforge.hl7.org/gf/project/ GForge])<br />
<br />
<br />
==Project Documents==<br />
*Link to working documents/[[Main_Page|wiki pages]]<br />
*Link to [http://gforge.hl7.org/gf/project/ project GForge]<br />
*Link to reference documentation on [http://gforge.hl7.org/gf/project/ GForge], HL7 Web site [http://www.hl7.org/special/Committees/claims/docs.cfm WG Documents/Presentations page], or external web pages<br />
<br />
<br />
<noinclude>==Categorization== </noinclude><br />
To include your Project Page in a category listing, just include a statement like <nowiki>[[Category:Active_Projects]]</nowiki><br />
[[Category:StyleGuides]]</div>Charliemccayhttps://wiki.hl7.org/w/index.php?title=SemanticHealthNet&diff=66075SemanticHealthNet2012-09-20T11:33:26Z<p>Charliemccay: </p>
<hr />
<div>This is an initial placeholder page for the HL7 contributions to the SemanticHealthNet project. <br />
<br />
Further details about the project can be found at http://www.semantichealthnet.eu/ or by contacting Charlie McCay (charlie@ramseysystems.co.uk).<br />
<br />
20th Sept 2012 update: <br />
Done:<br />
A draft Project scope statement has been circulated to the HL7 European Taskforce for review.<br />
A draft CDA instance for a Heart Failure Summary document has been created.<br />
Next Steps:<br />
Create a Heart Failure Summary CDA IG based on the requirements gathered by the project<br />
Improve project wiki page<br />
Create a FHIR IG based on the Heart Failure Summary requirements<br />
<br />
The SemanticHealthNet project is focused on organisational and governance processes, and is not resourced to create deployment-ready standards - however if the project is able to work with others to progress materials thorugh ballot then that would be a great outcome. Please get in touch with Charlie McCay (charlie@ramseysystems.co.uk) if you are interested in taking any of the SemanticHealthNet deliverables further, or you think that there are other projects happening in HL7 that SemanticHealthNet should eb engaged in.<br />
<br />
== Project Summary ==<br />
<br />
SemanticHealthNet will develop a scalable and sustainable pan-European organisational and governance process for the semantic interoperability of clinical and biomedical knowledge, to help ensure that EHR systems are optimised for patient care, public health and clinical research across healthcare systems and institutions.<br />
<br />
Through a clinically-driven workplan, exemplified in cardiovascular medicine, SemanticHealthNet will capture the needs for evidence-based, patient-centred integrated care and for public health, encapsulating existing European consensus in the management of chronic heart failure and cardiovascular prevention. Experts in EHR architectures, clinical data structures, terminologies and ontology will combine, tailor and pilot their best-of-breed resources in response to the needs articulated by clinicians and public health physicians.<br />
<br />
These exemplars will be cross-referenced with other domains and stakeholder perspectives via Clinical and Industrial Advisory Boards and interactions with other projects in Topic 5.3. The project will generalise and formalise the methods and best practices in how to combine and adapt informatics resources to support semantic interoperability, and how these can be developed and supported at scale. Health authorities, clinical professionals, ministries, vendors, purchasers, insurers are involved to ensure the project approach and results are realistically adoptable and viable, building on the SemanticHEALTH and CALLIOPE roadmaps.<br />
<br />
A business model to justify strategic investments, including the opportunity costs for key stakeholders such as SDOs, industry, will be defined. This, and links with epSOS II and the eHealth Governance Initiative, will inform the shape of the Virtual Organisation that this Network will establish to sustain semantic interoperability developments and their adoption.<br />
<br />
The consortium comprises more than 40 internationally recognised experts, including from USA and Canada, ensuring a global impact.</div>Charliemccayhttps://wiki.hl7.org/w/index.php?title=SemanticHealthNet&diff=60539SemanticHealthNet2012-03-29T13:50:01Z<p>Charliemccay: Created page with "This is an initial placeholder page for the HL7 contributions to the SemanticHealthNet project. Further details about the project can be found at http://www.semantichealthnet...."</p>
<hr />
<div>This is an initial placeholder page for the HL7 contributions to the SemanticHealthNet project. <br />
<br />
Further details about the project can be found at http://www.semantichealthnet.eu/ or by contacting Charlie McCay (charlie@ramseysystems.co.uk).<br />
<br />
<br />
<br />
SemanticHealthNet will develop a scalable and sustainable pan-European organisational and governance process for the semantic interoperability of clinical and biomedical knowledge, to help ensure that EHR systems are optimised for patient care, public health and clinical research across healthcare systems and institutions.<br />
<br />
Through a clinically-driven workplan, exemplified in cardiovascular medicine, SemanticHealthNet will capture the needs for evidence-based, patient-centred integrated care and for public health, encapsulating existing European consensus in the management of chronic heart failure and cardiovascular prevention. Experts in EHR architectures, clinical data structures, terminologies and ontology will combine, tailor and pilot their best-of-breed resources in response to the needs articulated by clinicians and public health physicians.<br />
<br />
These exemplars will be cross-referenced with other domains and stakeholder perspectives via Clinical and Industrial Advisory Boards and interactions with other projects in Topic 5.3. The project will generalise and formalise the methods and best practices in how to combine and adapt informatics resources to support semantic interoperability, and how these can be developed and supported at scale. Health authorities, clinical professionals, ministries, vendors, purchasers, insurers are involved to ensure the project approach and results are realistically adoptable and viable, building on the SemanticHEALTH and CALLIOPE roadmaps.<br />
<br />
A business model to justify strategic investments, including the opportunity costs for key stakeholders such as SDOs, industry, will be defined. This, and links with epSOS II and the eHealth Governance Initiative, will inform the shape of the Virtual Organisation that this Network will establish to sustain semantic interoperability developments and their adoption.<br />
<br />
The consortium comprises more than 40 internationally recognised experts, including from USA and Canada, ensuring a global impact.</div>Charliemccayhttps://wiki.hl7.org/w/index.php?title=GreenCDA_Project&diff=46658GreenCDA Project2011-02-11T10:13:40Z<p>Charliemccay: added link to project insight</p>
<hr />
<div>=Project scope=<br />
*Objectives: Create greenCDA modules for CCD.<br />
<br />
The Structured Documents Working Group will develop greenCDA modules for CCD. [http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=658 A Scope statement for the project is available with Project Insight no 658].<br />
<br />
=What is greenCDA?=<br />
<br />
The full specification of CDA XML addresses universal requirements for exchange and management of structured clinical documents. The greenCDA concept explores one method of working with an implementation-specific XML while maintaining the full utility of CDA, asserting as a primary principle that any simplification must also deliver valid, normative CDA (plain vanilla CDA). <br />
<br />
The concept is named “green CDA” because it’s good for the environment!<br />
<br />
=Project Materials=<br />
<br />
Current (HL7 ballot site):<br />
<br />
* [http://www.hl7.org/documentcenter/ballots/2010SEP/downloads/CDAR2_IG_GREENMOD4CCD_R1_I1_2010SEP.zip HL7 Implementation Guide for CDA Release 2: greenCDA Modules for CCD, Release 1 ] (zip)<br />
<br />
Outdated (historical reference only):<br />
<br />
* [http://wiki.hl7.org/images/f/f9/GreenCDA-synopsis.doc A 2p synopsis of the greenCDA white paper] (Word)<br />
* [http://wiki.hl7.org/images/1/14/GreenCDA.doc The greenCDA draft white paper] (word) <br />
* [http://wiki.hl7.org/images/3/37/GreenCDA.zip A zip file containing a sample Problem Act] (zip)<br />
<br />
Robert Worden has implemented the greenCDA sample in [http://wiki.hl7.org/index.php?title=Mu_ITS_Tool a prototype tool] to define, test, and deploy a Micro-ITS or Green CDA. The purpose of the tool is to encourage experimentation with Micro-ITS or Green CDA, to help elicit the full requirements for these facilities.</div>Charliemccayhttps://wiki.hl7.org/w/index.php?title=Product_CTS&diff=43861Product CTS2010-11-30T11:04:28Z<p>Charliemccay: /* Implementations/ Case Studies (Actual Users) */</p>
<hr />
<div>=Product Brief - CTS - Common Terminology Services=<br />
__TOC__<br />
back to [[Main_Page]]<br />
back to [[Product_List]]<br />
==Product Name - CTS - Common Terminology Services==<br />
<br />
===Topics===<br />
<br />
===Standard Category===<br />
Health Information Modeling Standards: V3 Foundation Vocabulary Domains<br />
<br />
===Integration Paradigm===<br />
SOA based terminology service, Services<br />
<br />
===Type===<br />
Normative, ANSI Standard, ISO Standard<br />
===Releases===<br />
* ANSI/HL7 V3 CTS, V1-2005; ISO/HL7 27951:2009(E)<br />
* [http://www.hl7.org/dstucomments/showdetail.cfm?dstuid=50 Common Terminology Services Release 2] HL7 V3 CTS, R2 - HL7 Version 3 Standard: Common Terminology Services, Release 2<br />
DSTU - Oct 2009<br />
<br />
===Summary===<br />
The HL7 Common Terminology Services (HL7 CTS) defines an Application Programming Interface (API)service interface that can be used by HL7 Version 3 software when accessing terminological content.<br />
<br />
===Description===<br />
The Common Terminology Services (CTS) specification was developed as an alternative to a common data structure. Instead of specifying what an external terminology must look like, HL7 has chosen to identify the common functional characteristics that an external terminology must be able to provide. As an example, an HL7 compliant terminology service will need to be able to determine whether a given concept code is valid within the particular resource. Instead of describing a table keyed by the resource identifier and concept code, the CTS specification describes an Application Programming Interface (API) call that takes a resource identifier and concept code as input and returns a true/false value. Each terminology developer is free to implement this API call in whatever way is most appropriate for them.<br />
<br />
Before proceeding, we need to first state some things that the CTS specification is not designed to do.<br />
<br />
*The current version of CTS is not intended to be a complete terminology service. The scope of CTS is restricted to the functionality needed to design, implement and deploy an HL7 Version 3 compliant software package. In much the same spirit as the XML/SGML relationship, the HL7 CTS is meant to represent a proper subset of functionality that may be provided by more sophisticated APIs such as that represented by the OMG TQS specification.<br />
<br />
*CTS is not intended to be a general purpose query language. It is intended to specify only the specific services needed in the HL7 implementation.<br />
<br />
*CTS does not specify how the service is to be implemented. It is intentionally silent when it comes to service advertising and discovery, establishing and maintaining connections, and the delivery and routing of messages. It is presumed that a CTS implementation will use the underlying architecture that is most appropriate for the given implementation circumstances.<br />
The Health Level Seven (HL7) Version 3 standards are based on a Reference Information Model (RIM) which is flexible and general in structure. Representation of information within this model is dependent on the availability of terminological resources which can be used to populate the properties of the model with appropriate semantic content. Whenever possible, the HL7 Version 3 Standard references existing terminological resources instead of attempting to create a new resource within the standard itself.<br />
<br />
These external terminological resources can vary considerably in both content and structure. The HL7 standard needs to be able to identify a minimum set of characteristics that any terminological resource must possess if it is to be used in a HL7 messaging environment. One approach to this task would be to specify a common data structure which all terminological resources would have to fit. This approach, however, is not without drawbacks. First, a common data structure would have to represent a ‘least common denominator’, which could mask more advanced content and functional characteristics that might be particular to a specific terminology. Another drawback is that this approach puts much of the responsibility for maintaining and updating the content on the HL7 standards body rather than the individual terminology developers.<br />
<br />
The Common Terminology Services (CTS) specification was developed as an alternative to a common data structure. Instead of specifying what an external terminology must look like, HL7 has chosen to identify the common functional characteristics that an external terminology must be able to provide. As an example, an HL7 compliant terminology service will need to be able to determine whether a given concept code is valid within the particular resource. Instead of describing a table keyed by the resource identifier and concept code, the CTS specification describes an Application Programming Interface (API) call that takes a resource identifier and concept code as input and returns a true/false value. Each terminology developer is free to implement this API call in whatever way is most appropriate for them.<br />
<br />
<br />
===Business Case (Intended Use, Customers)===<br />
* Terminology service users and providers<br />
<br />
===Benefits===<br />
* Benefits for designers and implementation developers<br />
** Software can be written once without the need to understand each terminology vendor’s database and/or API<br />
** Hides much of the complexity inherent in modern terminology systems.<br />
<br />
* Benefits for terminology software developers<br />
** Basic functional requirements for terminology services are clearly specified<br />
** Implementation can be based on existing databases and software<br />
** A common entry point to terminology content <br />
<br />
<br />
===Implementations/ Case Studies (Actual Users)===<br />
* Apelon, Inc. - Wrapper over DTS API<br />
* Intel SOA Expressway for Healthcare, which provides a standard CTS interface overtop of the open source Apelon DTS terminology engine. [http://software.intel.com/en-us/blogs/2008/10/02/designing-for-gray-scale-under-the-hood-of-medical-terminology-translation/] [http://software.intel.com/en-us/blogs/2008/09/23/semantic-normalization-making-sense-out-of-health-data/]<br />
* Mayo Clinic - Wrapper over LexEVS, and MS access for HL7<br />
* Centers for Disease Control and Prevention (CDC) Vocabulary Server - PHIN VADS [http://phinvads.cdc.gov], PHIN VADS Developer's Guide[http://phinvads.cdc.gov/vads/developersGuide.action], VADS online support forum [http://www.phconnect.org/group/phinvads]<br />
* HL7 implementation of CTS on GForge as the engine behind the Harmonization tool (not maintained since the alpha release)<br />
<br />
===Resources===<br />
<br />
<br />
====Work Groups====<br />
* [http://wiki.hl7.org/index.php?title=Vocabulary Vocabulary] WG<br />
<br />
====Education====<br />
* See more at http://www.hl7.org/implement/training.cfm<br />
* HL7 Vocabulary WG Advanced Terminology Tutorials<br />
<br />
=====Certification Available=====<br />
*none<br />
<br />
====Presentations====<br />
* HL7 Vocabulary WG Advanced Terminology Tutorials<br />
<br />
====Relationship to/ Dependencies on, other standards====<br />
* See CTS specification for details<br />
<br />
====Links to current projects in development====<br />
* ANSI/HL7 V3 CTS, V1-2005, currently under ISO ballot IS #27951 at [http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=483 Project Insight # 483]<br />
* [http://www.hl7.org/dstucomments/showdetail.cfm?dstuid=50 Common Terminology Services Release 2] at [http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=324 Project Insight # 324]<br />
[[Category:Products]]</div>Charliemccayhttps://wiki.hl7.org/w/index.php?title=Product_CTS&diff=43860Product CTS2010-11-30T11:03:45Z<p>Charliemccay: /* Implementations/ Case Studies (Actual Users) */</p>
<hr />
<div>=Product Brief - CTS - Common Terminology Services=<br />
__TOC__<br />
back to [[Main_Page]]<br />
back to [[Product_List]]<br />
==Product Name - CTS - Common Terminology Services==<br />
<br />
===Topics===<br />
<br />
===Standard Category===<br />
Health Information Modeling Standards: V3 Foundation Vocabulary Domains<br />
<br />
===Integration Paradigm===<br />
SOA based terminology service, Services<br />
<br />
===Type===<br />
Normative, ANSI Standard, ISO Standard<br />
===Releases===<br />
* ANSI/HL7 V3 CTS, V1-2005; ISO/HL7 27951:2009(E)<br />
* [http://www.hl7.org/dstucomments/showdetail.cfm?dstuid=50 Common Terminology Services Release 2] HL7 V3 CTS, R2 - HL7 Version 3 Standard: Common Terminology Services, Release 2<br />
DSTU - Oct 2009<br />
<br />
===Summary===<br />
The HL7 Common Terminology Services (HL7 CTS) defines an Application Programming Interface (API)service interface that can be used by HL7 Version 3 software when accessing terminological content.<br />
<br />
===Description===<br />
The Common Terminology Services (CTS) specification was developed as an alternative to a common data structure. Instead of specifying what an external terminology must look like, HL7 has chosen to identify the common functional characteristics that an external terminology must be able to provide. As an example, an HL7 compliant terminology service will need to be able to determine whether a given concept code is valid within the particular resource. Instead of describing a table keyed by the resource identifier and concept code, the CTS specification describes an Application Programming Interface (API) call that takes a resource identifier and concept code as input and returns a true/false value. Each terminology developer is free to implement this API call in whatever way is most appropriate for them.<br />
<br />
Before proceeding, we need to first state some things that the CTS specification is not designed to do.<br />
<br />
*The current version of CTS is not intended to be a complete terminology service. The scope of CTS is restricted to the functionality needed to design, implement and deploy an HL7 Version 3 compliant software package. In much the same spirit as the XML/SGML relationship, the HL7 CTS is meant to represent a proper subset of functionality that may be provided by more sophisticated APIs such as that represented by the OMG TQS specification.<br />
<br />
*CTS is not intended to be a general purpose query language. It is intended to specify only the specific services needed in the HL7 implementation.<br />
<br />
*CTS does not specify how the service is to be implemented. It is intentionally silent when it comes to service advertising and discovery, establishing and maintaining connections, and the delivery and routing of messages. It is presumed that a CTS implementation will use the underlying architecture that is most appropriate for the given implementation circumstances.<br />
The Health Level Seven (HL7) Version 3 standards are based on a Reference Information Model (RIM) which is flexible and general in structure. Representation of information within this model is dependent on the availability of terminological resources which can be used to populate the properties of the model with appropriate semantic content. Whenever possible, the HL7 Version 3 Standard references existing terminological resources instead of attempting to create a new resource within the standard itself.<br />
<br />
These external terminological resources can vary considerably in both content and structure. The HL7 standard needs to be able to identify a minimum set of characteristics that any terminological resource must possess if it is to be used in a HL7 messaging environment. One approach to this task would be to specify a common data structure which all terminological resources would have to fit. This approach, however, is not without drawbacks. First, a common data structure would have to represent a ‘least common denominator’, which could mask more advanced content and functional characteristics that might be particular to a specific terminology. Another drawback is that this approach puts much of the responsibility for maintaining and updating the content on the HL7 standards body rather than the individual terminology developers.<br />
<br />
The Common Terminology Services (CTS) specification was developed as an alternative to a common data structure. Instead of specifying what an external terminology must look like, HL7 has chosen to identify the common functional characteristics that an external terminology must be able to provide. As an example, an HL7 compliant terminology service will need to be able to determine whether a given concept code is valid within the particular resource. Instead of describing a table keyed by the resource identifier and concept code, the CTS specification describes an Application Programming Interface (API) call that takes a resource identifier and concept code as input and returns a true/false value. Each terminology developer is free to implement this API call in whatever way is most appropriate for them.<br />
<br />
<br />
===Business Case (Intended Use, Customers)===<br />
* Terminology service users and providers<br />
<br />
===Benefits===<br />
* Benefits for designers and implementation developers<br />
** Software can be written once without the need to understand each terminology vendor’s database and/or API<br />
** Hides much of the complexity inherent in modern terminology systems.<br />
<br />
* Benefits for terminology software developers<br />
** Basic functional requirements for terminology services are clearly specified<br />
** Implementation can be based on existing databases and software<br />
** A common entry point to terminology content <br />
<br />
<br />
===Implementations/ Case Studies (Actual Users)===<br />
* Apelon, Inc. - Wrapper over DTS API<br />
* Intel SOA Expressway for Healthcare, which provides a standard CTS interface overtop of the open source Apelon DTS terminology engine. [http://software.intel.com/en-us/blogs/2008/10/02/designing-for-gray-scale-under-the-hood-of-medical-terminology-translation/<br />
] [<br />
http://software.intel.com/en-us/blogs/2008/09/23/semantic-normalization-making-sense-out-of-health-data/ ]<br />
* Mayo Clinic - Wrapper over LexEVS, and MS access for HL7<br />
* Centers for Disease Control and Prevention (CDC) Vocabulary Server - PHIN VADS [http://phinvads.cdc.gov], PHIN VADS Developer's Guide[http://phinvads.cdc.gov/vads/developersGuide.action], VADS online support forum [http://www.phconnect.org/group/phinvads]<br />
* HL7 implementation of CTS on GForge as the engine behind the Harmonization tool (not maintained since the alpha release)<br />
<br />
===Resources===<br />
<br />
<br />
====Work Groups====<br />
* [http://wiki.hl7.org/index.php?title=Vocabulary Vocabulary] WG<br />
<br />
====Education====<br />
* See more at http://www.hl7.org/implement/training.cfm<br />
* HL7 Vocabulary WG Advanced Terminology Tutorials<br />
<br />
=====Certification Available=====<br />
*none<br />
<br />
====Presentations====<br />
* HL7 Vocabulary WG Advanced Terminology Tutorials<br />
<br />
====Relationship to/ Dependencies on, other standards====<br />
* See CTS specification for details<br />
<br />
====Links to current projects in development====<br />
* ANSI/HL7 V3 CTS, V1-2005, currently under ISO ballot IS #27951 at [http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=483 Project Insight # 483]<br />
* [http://www.hl7.org/dstucomments/showdetail.cfm?dstuid=50 Common Terminology Services Release 2] at [http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=324 Project Insight # 324]<br />
[[Category:Products]]</div>Charliemccayhttps://wiki.hl7.org/w/index.php?title=Product_CTS&diff=43657Product CTS2010-11-24T09:34:40Z<p>Charliemccay: /* Implementations/ Case Studies (Actual Users) */</p>
<hr />
<div>=Product Brief - CTS - Common Terminology Services=<br />
__TOC__<br />
back to [[Main_Page]]<br />
back to [[Product_List]]<br />
==Product Name - CTS - Common Terminology Services==<br />
<br />
===Topics===<br />
<br />
===Standard Category===<br />
Health Information Modeling Standards: V3 Foundation Vocabulary Domains<br />
<br />
===Integration Paradigm===<br />
SOA based terminology service, Services<br />
<br />
===Type===<br />
Normative, ANSI Standard, ISO Standard<br />
===Releases===<br />
* ANSI/HL7 V3 CTS, V1-2005; ISO/HL7 27951:2009(E)<br />
* [http://www.hl7.org/dstucomments/showdetail.cfm?dstuid=50 Common Terminology Services Release 2] HL7 V3 CTS, R2 - HL7 Version 3 Standard: Common Terminology Services, Release 2<br />
DSTU - Oct 2009<br />
<br />
===Summary===<br />
The HL7 Common Terminology Services (HL7 CTS) defines an Application Programming Interface (API)service interface that can be used by HL7 Version 3 software when accessing terminological content.<br />
<br />
===Description===<br />
The Common Terminology Services (CTS) specification was developed as an alternative to a common data structure. Instead of specifying what an external terminology must look like, HL7 has chosen to identify the common functional characteristics that an external terminology must be able to provide. As an example, an HL7 compliant terminology service will need to be able to determine whether a given concept code is valid within the particular resource. Instead of describing a table keyed by the resource identifier and concept code, the CTS specification describes an Application Programming Interface (API) call that takes a resource identifier and concept code as input and returns a true/false value. Each terminology developer is free to implement this API call in whatever way is most appropriate for them.<br />
<br />
Before proceeding, we need to first state some things that the CTS specification is not designed to do.<br />
<br />
*The current version of CTS is not intended to be a complete terminology service. The scope of CTS is restricted to the functionality needed to design, implement and deploy an HL7 Version 3 compliant software package. In much the same spirit as the XML/SGML relationship, the HL7 CTS is meant to represent a proper subset of functionality that may be provided by more sophisticated APIs such as that represented by the OMG TQS specification.<br />
<br />
*CTS is not intended to be a general purpose query language. It is intended to specify only the specific services needed in the HL7 implementation.<br />
<br />
*CTS does not specify how the service is to be implemented. It is intentionally silent when it comes to service advertising and discovery, establishing and maintaining connections, and the delivery and routing of messages. It is presumed that a CTS implementation will use the underlying architecture that is most appropriate for the given implementation circumstances.<br />
The Health Level Seven (HL7) Version 3 standards are based on a Reference Information Model (RIM) which is flexible and general in structure. Representation of information within this model is dependent on the availability of terminological resources which can be used to populate the properties of the model with appropriate semantic content. Whenever possible, the HL7 Version 3 Standard references existing terminological resources instead of attempting to create a new resource within the standard itself.<br />
<br />
These external terminological resources can vary considerably in both content and structure. The HL7 standard needs to be able to identify a minimum set of characteristics that any terminological resource must possess if it is to be used in a HL7 messaging environment. One approach to this task would be to specify a common data structure which all terminological resources would have to fit. This approach, however, is not without drawbacks. First, a common data structure would have to represent a ‘least common denominator’, which could mask more advanced content and functional characteristics that might be particular to a specific terminology. Another drawback is that this approach puts much of the responsibility for maintaining and updating the content on the HL7 standards body rather than the individual terminology developers.<br />
<br />
The Common Terminology Services (CTS) specification was developed as an alternative to a common data structure. Instead of specifying what an external terminology must look like, HL7 has chosen to identify the common functional characteristics that an external terminology must be able to provide. As an example, an HL7 compliant terminology service will need to be able to determine whether a given concept code is valid within the particular resource. Instead of describing a table keyed by the resource identifier and concept code, the CTS specification describes an Application Programming Interface (API) call that takes a resource identifier and concept code as input and returns a true/false value. Each terminology developer is free to implement this API call in whatever way is most appropriate for them.<br />
<br />
<br />
===Business Case (Intended Use, Customers)===<br />
* Terminology service users and providers<br />
<br />
===Benefits===<br />
* Benefits for designers and implementation developers<br />
** Software can be written once without the need to understand each terminology vendor’s database and/or API<br />
** Hides much of the complexity inherent in modern terminology systems.<br />
<br />
* Benefits for terminology software developers<br />
** Basic functional requirements for terminology services are clearly specified<br />
** Implementation can be based on existing databases and software<br />
** A common entry point to terminology content <br />
<br />
<br />
===Implementations/ Case Studies (Actual Users)===<br />
* Apelon, Inc. - Wrapper over DTS API<br />
* Intel<br />
* Mayo Clinic - Wrapper over LexEVS<br />
* CDC PHIN VADIS - http://www.phconnect.org/group/phinvads/forum/topic/listForTag?tag=CTS<br />
<br />
===Resources===<br />
<br />
<br />
====Work Groups====<br />
* [http://wiki.hl7.org/index.php?title=Vocabulary Vocabulary] WG<br />
<br />
====Education====<br />
* See more at http://www.hl7.org/implement/training.cfm<br />
* HL7 Vocabulary WG Advanced Terminology Tutorials<br />
<br />
=====Certification Available=====<br />
*none<br />
<br />
====Presentations====<br />
* HL7 Vocabulary WG Advanced Terminology Tutorials<br />
<br />
====Relationship to/ Dependencies on, other standards====<br />
* See CTS specification for details<br />
<br />
====Links to current projects in development====<br />
* ANSI/HL7 V3 CTS, V1-2005, currently under ISO ballot IS #27951 at [http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=483 Project Insight # 483]<br />
* [http://www.hl7.org/dstucomments/showdetail.cfm?dstuid=50 Common Terminology Services Release 2] at [http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=324 Project Insight # 324]<br />
[[Category:Products]]</div>Charliemccayhttps://wiki.hl7.org/w/index.php?title=CTS&diff=43656CTS2010-11-24T09:32:55Z<p>Charliemccay: </p>
<hr />
<div>Common Terminology Services is both the name of a project as well as of a specification. <br />
<br />
The project has published a CTS specification, known as Release 1, or CTS I, and is working on Release 2, known as CTS 2.<br />
<br />
There is a product description with much more detail available at [[Product_CTS]] <br />
<br />
== CTS 2 (Release 2 of Common Terminology Services) ==<br />
*[[CTS2|Common Terminology Services 2.0]]<br />
<br />
== CTS I (Release 1 of Common Terminology Services) ==<br />
*[[CTS Conformance]] <br />
*[[CTS Q&A]] <br />
*[[Errata and fixes]] <br />
*[[CTS Implementation|Common Terminology Services - Implementation]]</div>Charliemccayhttps://wiki.hl7.org/w/index.php?title=CTS&diff=43655CTS2010-11-24T09:32:24Z<p>Charliemccay: </p>
<hr />
<div>Common Terminology Services is both the name of a project as well as of a specification. <br />
<br />
The project has published a CTS specification, known as Release 1, or CTS I, and is working on Release 2, known as CTS 2.<br />
<br />
There is a product description with much more detail available at http://wiki.hl7.org/index.php?title=Product_CTS <br />
<br />
== CTS 2 (Release 2 of Common Terminology Services) ==<br />
*[[CTS2|Common Terminology Services 2.0]]<br />
<br />
== CTS I (Release 1 of Common Terminology Services) ==<br />
*[[CTS Conformance]] <br />
*[[CTS Q&A]] <br />
*[[Errata and fixes]] <br />
*[[CTS Implementation|Common Terminology Services - Implementation]]</div>Charliemccayhttps://wiki.hl7.org/w/index.php?title=Architecture_Board_2010&diff=34947Architecture Board 20102010-03-30T14:00:31Z<p>Charliemccay: /* ArB Communication Venues */ typo may->many</p>
<hr />
<div>The Architecture Board is responsible for the architecture of the HL7 Standards. <br />
<br />
= ArB Mission = <br />
<br />
The HL7 ArB seeks to define a [[Architecture|coherent architecture for HL7 work]] that defines the relationships among the HL7 work products and how they relate to other standards and components of local implementations. This architecture includes the Business Architecture by which these work products are produced and managed through their life cycle, the governance that will be enacted on these work products, and the scope of the standardization effort itself.<br />
<br />
<br />
<br />
= ArB Scope =<br />
<br />
The scope of the ArB's work covers:<br />
* Defining a [[Architecture|coherent standards architecture for HL7]] to strive towards.<br />
* Working within the organization to market and refine the architecture <br />
* Ongoing interaction with HL7 customers to market and refine the architecture <br />
* Consideration of the suitability of the organisational structures to deliver the architecture<br />
* Defining the procedures and compliance criteria that ensure the HL7 work products conform to the architecture to enable the achievement stated levels of interoperability<br />
* Tracks developments in underlying SDO's and standards and keeps HL7 appropriately informed<br />
==Current Activities==<br />
*Projects<br />
**[[SAIF_main_page | SAIF/SAEAF]]<br />
**[[ArB review of other material]]<br />
*[[Arb_meeting_schedule | Meeting Schedule and Minutes]]<br />
*[http://gforge.hl7.org/gf/project/saeaf/tracker/?action=TrackerItemBrowse&tracker_id=590 Action Items ]<br />
*Links - those that contextualize Arb <br />
**TSC communications that frame our activities(TBD)<br />
**Terms of Reference(TBD)<br />
<br />
[[Category:ARB_work_in_progress]]<br />
<br />
[[User:Ajulian|Tony Julian]] 17:59, 18 March 2010 (UTC)<br />
<br />
== ArB Communication Venues ==<br />
The many venues ArB uses for communication are found at [[20100322_arb_communication_venues| Communications]].<br />
[[Category:Arb_Deprecated_item]][[Category:ARB_work_in_progress]][[Category:Arb Minutes]] [[Category:Arb Old Minutes]][[Category:arb_done_item]]</div>Charliemccayhttps://wiki.hl7.org/w/index.php?title=20100322_arb_communication_venues&diff=3494320100322 arb communication venues2010-03-30T10:07:10Z<p>Charliemccay: /* Gforge SVN Repository */ removed second "=" as resulted in broken link</p>
<hr />
<div>{{Arb Done Item}}<br />
<br />
=Communication Venues=<br />
== email list ==<br />
<br />
The main internal communication resource for [[Architecture_Board | ArB]] is the HL7 email list. Subscription to the email list is through the HL7 listserver page at [http://www.hl7.org/listservice/index.cfm http://www.hl7.org/listservice/index.cfm] , and is open to all HL7 members and non-members.<br />
<br />
== Teleconferences ==<br />
<br />
The [[Architecture_Board | ArB]] holds regular (weekly) teleconferences to discuss the various projects we are working on. Both regular and special teleconferences are announced on the email list.<br />
A partial list of teleconferences may be found at [[Arb_meeting_schedule|Meeting Schedule]].<br />
<br />
The official teleconference schedule may be found at [[http://www.hl7.org/concalls/index.cfm?action==home.welcome| HL7 Conference Call Center]].<br />
<br />
<br />
<br />
NOTE: To see ONLY the [[Architecture_Board | ArB]] calls, on the left frame select View Options, then press the Reset Button. Check the Architectural Review box, then press the View these . . button.<br />
<br />
== Wiki ==<br />
<br />
The [[Architecture_Board | ArB]] wiki can be found at [http://wiki.hl7.org/index.php?title==Architecture_Board http://wiki.hl7.org/index.php?title==Architecture_Board]. <br />
This document is hosted and maintainted on the wiki. The wiki is used for all internal & procedural documentation, for meeting agendas and minutes, and for working project documentation.<br />
<br />
== Skype channel ==<br />
<br />
[[Architecture_Board | ArB]] uses a skype channel to help organise teleconferences, and to assist with communications during the teleconferences. The skype channel is open to regular contributers. To join the skype channel, send an email request to any regular [[Architecture_Board | ArB]] member. Skype may be downloaded for free from [http://skype.com http://skype.com].<br />
<br />
== Official Blog ==<br />
<br />
Official positions of, or guidance from, the [[Architecture_Board | ArB]] that are of interest to the HL7 or <br />
related standards communities are published in the [[Architecture_Board | ArB]] blog at [http://hl7-arb.blogspot.com http://hl7-arb.blogspot.com] . Any member of the [[Architecture_Board | ArB]] may post at the blog, but content is only posted to the blog following approval during an [[Architecture_Board | ArB]] meeting or by ArB member consensus on the [[Architecture_Board | ArB]] email list.<br />
<br />
== Open Meetings == <br />
<br />
[[Architecture_Board | ArB]] meets regularly at normal HL7 working group meetings, and occasionally otherwise. Unless specifically announced, all [[Architecture_Board | ArB]] meetings are open to other HL7 members. <br />
<br />
== HL7 communications resources ==<br />
<br />
[[Architecture_Board | ArB]] may also make use of official HQ or TSC communication resources, to either communicate directly with the committees, the membership, or to make official press releases. These communication resources are rarely used, and only when appropriate for the subject matter.<br />
<br />
== Gforge SVN Repository ==<br />
<br />
All documents are archived in the HL7 Gforge repository at [http://gforge.hl7.org/gf]. For current publications refer to [[http://gforge.hl7.org/gf/project/saeaf/docman/?subdir=258 |work under peer review 2010_03]].<br />
[[Category:arb_done_item]][[User:ajulian|Tony Julian]]</div>Charliemccayhttps://wiki.hl7.org/w/index.php?title=Talk:CDA_R3_NonXMLBody-Text_Cardinality&diff=30442Talk:CDA R3 NonXMLBody-Text Cardinality2009-12-31T12:53:29Z<p>Charliemccay: </p>
<hr />
<div>charliemccay: I am not sure that having multiple .text attributes makes sense - but I do support having multiple renderings of the document - this could be achieved by having 1..* for bodyChoice -- the bodies would all be renderings of the same document (eg Word and PDF)<br />
In a similar way I would like to see the rendering separated from the entries in the RHS (and more than one rendering being possible), and maybe alternate renderings could be conveyed as NonXMLBody. By rendering I mean the narrative content - not (just) then the CDA markup has been transformed to HTML or PDF for display.</div>Charliemccayhttps://wiki.hl7.org/w/index.php?title=Talk:CDA_R3_NonXMLBody-Text_Cardinality&diff=30441Talk:CDA R3 NonXMLBody-Text Cardinality2009-12-31T12:51:25Z<p>Charliemccay: New page: charliemccay: I am not sure that having multiple .text attributes makes sense - but I do support having multiple renderings of the document - this could be achieved by having 1..* for body...</p>
<hr />
<div>charliemccay: I am not sure that having multiple .text attributes makes sense - but I do support having multiple renderings of the document - this could be achieved by having 1..* for bodyChoice -- the bodies would all be renderings of the same document (eg Word and PDF)<br />
In a similar way I would like to see the rendering separated from the entries in the RHS, and maybe alternate renderings could be conveyed as NonXMLBody.</div>Charliemccayhttps://wiki.hl7.org/w/index.php?title=CEN_ISO_HL7_Joint_Initiative&diff=26687CEN ISO HL7 Joint Initiative2009-09-16T14:17:36Z<p>Charliemccay: </p>
<hr />
<div>The HL7 status of JIC and related standards activity is maintained at http://www.hl7tsc.org/wiki/index.php?title=ISO_and_JIC_projects<br />
<br />
The website for the Joint initiative may be found at http://www.global-e-health-standards.org/<br />
<br />
HL7 contributions tracked as TSC issues at [http://hl7projects.hl7.nscee.edu/tracker/?func=browse&group_id=52&atid=313]<br />
<br />
The full set of HL7 projects (including is found at http://hl7projects.hl7.nscee.edu/frs/?group_id=52<br />
<br />
<br />
<br />
== projects ==<br />
<br />
* datatypes [[ISO Datatypes]]<br />
* see the joint initiative website and full HL7 project list above for other joint projects (or they could be added here)</div>Charliemccayhttps://wiki.hl7.org/w/index.php?title=Xml_schema_enhancement&diff=20803Xml schema enhancement2008-11-27T13:02:40Z<p>Charliemccay: New page: placeholder wiki page for schema enhancement investigation</p>
<hr />
<div>placeholder wiki page for schema enhancement investigation</div>Charliemccayhttps://wiki.hl7.org/w/index.php?title=ITS_WG&diff=20802ITS WG2008-11-27T13:01:45Z<p>Charliemccay: /* ITS SIG Projects */</p>
<hr />
<div>The XML SIG was renamed the ITS SIG in Jan 2007, wiki content from the XML SIG is found [[XML related issues | here]]. <br />
<br />
The ITS SIG supports the HL7 mission through the development of Implementable Technology Specifications and Messaging Protocol guidelines (e.g. ebXML, Webservices, MLLP, ..) to be used when putting the HL7 information specifications to use.<br />
<br />
Sponsoring TCs are [[Infrastructure and Messaging TC]] and [[Structured Documents TC]]<br />
<br />
==== Specifications maintained by the ITS SIG ====<br />
This is a first cut of the list - it needs to be updated with links to the balloted versions, and to any work in progress. I am also not convinced that it is complete. There is a list maintained in the INM section of the wiki of who is responsible for various documents [[INM_Work_Distribution#Implementable_Technology_Specifications_.28ITS_SIG.29]]<br />
<br />
* ebXML transport protocol<br />
* [[web services transport protocol]]<br />
* [[removable media transport protocol]]<br />
* MLLP transport protocol (R2, normative)<br />
* [[XML related issues|XML ITS (release 1)]]<br />
* v2 pipe-bar ITS sections in chapter 2<br />
* v2 XML ITS document<br />
* [[ITS possibilities not active]]<br />
<br />
==== ITS SIG Projects ====<br />
* [[ISO Datatypes]] -- this is part of the [[New ITS project]]<br />
* [[New ITS project]]<br />
* [[XML ITS Structures r1.1]]<br />
* Glossary Entry for [[ITS]]<br />
* [[ITS SIG action items]]<br />
* [[HSSP product review]]<br />
* [[web services release 2]] -- committee due<br />
* [[ebxml release 2]] -- membership <br />
* [[removable media]] -- committee due<br />
* [[xml its datatypes r2]] -- parked<br />
* [[xml schema enhancement]]<br />
<br />
==== ITS SIG meetings ====<br />
===== Conference Calls =====<br />
* no calls currently schedued<br />
* wednesday 4pm ITS SIG calls. Where there is no other agenda item, the ballot reconcilliation calls are recorded on the wiki page below<br />
** [[ITS SIG Recon Calls]] (attendance and dialin details)<br />
*[[ITS SIG telcon 20080305]]<br />
*[[ITS SIG telcon 20080130]]<br />
* wednesday 4pm Wednesday calls joint with INM for datatypes reconciliation<br />
*[[ITS SIG INM TC Datatypes recon calls]]<br />
* conference call scheduled for Mondays 12am every week<br />
*[[ITS SIG telcon 20070806]]<br />
*[[ITS SIG telcon 20070730]]<br />
*[[ITS SIG telcon 20070716]]<br />
*[[ITS SIG telcon 20070709]]<br />
*[[ITS SIG telcon 20070702]]<br />
* some calls with notes to be produced<br />
*[[ITS SIG telcon 20070702]]<br />
*[[ITS SIG telcon 20070514 agenda]] <br />
* Cologne WGM<br />
*[[ITS SIG telcon 20070328 agenda]] [[ITS SIG telcon 20070328 notes]] 7am eastern - next call<br />
*[[ITS SIG telcon 20070319 agenda]] [[ITS SIG telcon 20070319 notes]] 11am eastern <br />
*[[ITS SIG telcon 20070314 notes]] 7am eastern <br />
*[[ITS SIG telcon 20070305 notes]] 11am eastern <br />
*[[ITS SIG telcon 20070228 agenda]] [[ITS SIG telcon 20070228 notes]] no meeting - lack of quorum<br />
*[[ITS SIG telcon 20070226 agenda]]<br />
*[[ITS SIG telcon 20070219 notes]]<br />
*[[ITS SIG telcon 20070205 agenda]]<br />
*[[ITS SIG telcon 20070131 agenda]]<br />
*[[ITS SIG telcon 20070124 agenda]]<br />
<br />
===== WGMs =====<br />
*[[ITS SIG May 2008 WGM agenda]]<br />
*[[ITS SIG Sept 2007 WGM agenda]]<br />
*[[ITS SIG May 2007 WGM agenda]]<br />
*[[XML San Diego 2007 Agenda]]<br />
<br />
==== Admin ====<br />
* [[XML to ITS SIG changeover issues]]<br />
*[[ITS SIG co-chairs tasklist]]<br />
* [[XML related issues]] (previous content of this page has been moved here)<br />
<br />
==== May 2007 Ballot Preparation ====<br />
*[[http://www.hl7.org/documentcenter/public/schedules/Pubs_Schedule_2007.pdf ballot timetable]]<br />
*[[ITS 2007MAY advanced CBC]] -- announcement for ITS ballots in May<br />
* need intent to ballot document done by feb 11th http://www.hl7.org/Library/Committees/xml/ITS%5FSIG%5FNIB%5FMAY%5F2007%2Ezip package of Notification of intent to ballot documents -- submitted by email and accepted by Don Lloyd. The ebXML and removable media documents have been superseeded by documents submitted by Doug Pratt.<br />
* First draft content - 25th Feb<br />
* [[EbXML_C1_Ballot_Spreadsheet_with_proposed_resolutions]]<br />
<br />
{{SIG Category}}<br />
<br />
<br />
==== September 2007 Ballot Preparation ====<br />
* Draft XML ITS V3 Structures R1.1 [[http://www.hl7.org/Library/Committees/xml/xmlitsR1%2E1%2Ezip]] [[Draft Appendix: ITS R1.1 Extensibility Implementation Considerations]]<br />
* Draft New ITS specification [[http://www.hl7.org/Library/Committees/xml/NewITSSpecRelease1%2E1%2Ezip]]<br />
* Draft New ITS Guide [[http://www.hl7.org/Library/Committees/xml/NewITSGuide%2Exml]]</div>Charliemccayhttps://wiki.hl7.org/w/index.php?title=ITS_WG&diff=20438ITS WG2008-11-11T17:39:25Z<p>Charliemccay: /* Conference Calls */</p>
<hr />
<div>The XML SIG was renamed the ITS SIG in Jan 2007, wiki content from the XML SIG is found [[XML related issues | here]]. <br />
<br />
The ITS SIG supports the HL7 mission through the development of Implementable Technology Specifications and Messaging Protocol guidelines (e.g. ebXML, Webservices, MLLP, ..) to be used when putting the HL7 information specifications to use.<br />
<br />
Sponsoring TCs are [[Infrastructure and Messaging TC]] and [[Structured Documents TC]]<br />
<br />
==== Specifications maintained by the ITS SIG ====<br />
This is a first cut of the list - it needs to be updated with links to the balloted versions, and to any work in progress. I am also not convinced that it is complete. There is a list maintained in the INM section of the wiki of who is responsible for various documents [[INM_Work_Distribution#Implementable_Technology_Specifications_.28ITS_SIG.29]]<br />
<br />
* ebXML transport protocol<br />
* [[web services transport protocol]]<br />
* [[removable media transport protocol]]<br />
* MLLP transport protocol (R2, normative)<br />
* [[XML related issues|XML ITS (release 1)]]<br />
* v2 pipe-bar ITS sections in chapter 2<br />
* v2 XML ITS document<br />
* [[ITS possibilities not active]]<br />
<br />
==== ITS SIG Projects ====<br />
* [[ISO Datatypes]] -- this is part of the [[New ITS project]]<br />
* [[New ITS project]]<br />
* [[XML ITS Structures r1.1]]<br />
* Glossary Entry for [[ITS]]<br />
* [[ITS SIG action items]]<br />
* [[HSSP product review]]<br />
* [[web services release 2]] -- committee due<br />
* [[ebxml release 2]] -- membership <br />
* [[removable media]] -- committee due<br />
* [[xml its datatypes r2]] -- parked<br />
<br />
==== ITS SIG meetings ====<br />
===== Conference Calls =====<br />
* no calls currently schedued<br />
* wednesday 4pm ITS SIG calls. Where there is no other agenda item, the ballot reconcilliation calls are recorded on the wiki page below<br />
** [[ITS SIG Recon Calls]] (attendance and dialin details)<br />
*[[ITS SIG telcon 20080305]]<br />
*[[ITS SIG telcon 20080130]]<br />
* wednesday 4pm Wednesday calls joint with INM for datatypes reconciliation<br />
*[[ITS SIG INM TC Datatypes recon calls]]<br />
* conference call scheduled for Mondays 12am every week<br />
*[[ITS SIG telcon 20070806]]<br />
*[[ITS SIG telcon 20070730]]<br />
*[[ITS SIG telcon 20070716]]<br />
*[[ITS SIG telcon 20070709]]<br />
*[[ITS SIG telcon 20070702]]<br />
* some calls with notes to be produced<br />
*[[ITS SIG telcon 20070702]]<br />
*[[ITS SIG telcon 20070514 agenda]] <br />
* Cologne WGM<br />
*[[ITS SIG telcon 20070328 agenda]] [[ITS SIG telcon 20070328 notes]] 7am eastern - next call<br />
*[[ITS SIG telcon 20070319 agenda]] [[ITS SIG telcon 20070319 notes]] 11am eastern <br />
*[[ITS SIG telcon 20070314 notes]] 7am eastern <br />
*[[ITS SIG telcon 20070305 notes]] 11am eastern <br />
*[[ITS SIG telcon 20070228 agenda]] [[ITS SIG telcon 20070228 notes]] no meeting - lack of quorum<br />
*[[ITS SIG telcon 20070226 agenda]]<br />
*[[ITS SIG telcon 20070219 notes]]<br />
*[[ITS SIG telcon 20070205 agenda]]<br />
*[[ITS SIG telcon 20070131 agenda]]<br />
*[[ITS SIG telcon 20070124 agenda]]<br />
<br />
===== WGMs =====<br />
*[[ITS SIG May 2008 WGM agenda]]<br />
*[[ITS SIG Sept 2007 WGM agenda]]<br />
*[[ITS SIG May 2007 WGM agenda]]<br />
*[[XML San Diego 2007 Agenda]]<br />
<br />
==== Admin ====<br />
* [[XML to ITS SIG changeover issues]]<br />
*[[ITS SIG co-chairs tasklist]]<br />
* [[XML related issues]] (previous content of this page has been moved here)<br />
<br />
==== May 2007 Ballot Preparation ====<br />
*[[http://www.hl7.org/documentcenter/public/schedules/Pubs_Schedule_2007.pdf ballot timetable]]<br />
*[[ITS 2007MAY advanced CBC]] -- announcement for ITS ballots in May<br />
* need intent to ballot document done by feb 11th http://www.hl7.org/Library/Committees/xml/ITS%5FSIG%5FNIB%5FMAY%5F2007%2Ezip package of Notification of intent to ballot documents -- submitted by email and accepted by Don Lloyd. The ebXML and removable media documents have been superseeded by documents submitted by Doug Pratt.<br />
* First draft content - 25th Feb<br />
* [[EbXML_C1_Ballot_Spreadsheet_with_proposed_resolutions]]<br />
<br />
{{SIG Category}}<br />
<br />
<br />
==== September 2007 Ballot Preparation ====<br />
* Draft XML ITS V3 Structures R1.1 [[http://www.hl7.org/Library/Committees/xml/xmlitsR1%2E1%2Ezip]] [[Draft Appendix: ITS R1.1 Extensibility Implementation Considerations]]<br />
* Draft New ITS specification [[http://www.hl7.org/Library/Committees/xml/NewITSSpecRelease1%2E1%2Ezip]]<br />
* Draft New ITS Guide [[http://www.hl7.org/Library/Committees/xml/NewITSGuide%2Exml]]</div>Charliemccayhttps://wiki.hl7.org/w/index.php?title=CEN_ISO_HL7_Joint_Initiative&diff=16807CEN ISO HL7 Joint Initiative2008-05-08T17:25:02Z<p>Charliemccay: </p>
<hr />
<div>The website for the Joint initiative may be found at http://www.global-e-health-standards.org/<br />
<br />
HL7 contributions tracked as TSC issues at [http://hl7projects.hl7.nscee.edu/tracker/?func=browse&group_id=52&atid=313]<br />
<br />
The full set of HL7 projects (including is found at http://hl7projects.hl7.nscee.edu/frs/?group_id=52<br />
<br />
== projects ==<br />
<br />
* datatypes [[ISO Datatypes]]<br />
* see the joint initiative website and full HL7 project list above for other joint projects (or they could be added here)</div>Charliemccayhttps://wiki.hl7.org/w/index.php?title=CEN_ISO_HL7_Joint_Initiative&diff=16806CEN ISO HL7 Joint Initiative2008-05-08T17:15:22Z<p>Charliemccay: </p>
<hr />
<div>The website for the Joint initiative may be found at http://www.global-e-health-standards.org/<br />
<br />
HL7 contributions tracked as TSC issues at [http://hl7projects.hl7.nscee.edu/tracker/?func=browse&group_id=52&atid=313]<br />
<br />
The full set of HL7 projects (including is found at http://hl7projects.hl7.nscee.edu/frs/?group_id=52<br />
<br />
== projects ==<br />
<br />
* datatypes [[ISO Datatypes]]</div>Charliemccayhttps://wiki.hl7.org/w/index.php?title=ITS_SIG_May_2008_WGM_agenda&diff=16665ITS SIG May 2008 WGM agenda2008-04-17T09:50:46Z<p>Charliemccay: </p>
<hr />
<div>The ITS SIG is meeting wed PM and thursday<br />
This is a placeholder for the detailed agenda<br />
<br />
<br />
Dear Co-Chairs,<br />
<br />
In order to have your committee’s agenda printed and available for handout on-site at the May Working Group Meeting in Phoenix, you must email that agenda to HL7 HQ (maryann@HL7.org) no later than the end of the day, Monday, April 28, 2008. Agendas received after this point will not be printed in the HL7 Agenda packet. To avoid confusion, please designate only one co-chair from each committee to send in the agenda.<br />
<br />
In addition, if your committee has not already done so, please upload the meeting minutes from the September Working Group Meeting. You can do so by going to: <br />
<br />
http://www.hl7.org/Lib_admin/minutesform.cfm<br />
<br />
<br />
Your help is greatly appreciated. Thank you for your participation and cooperation.<br />
<br />
<br />
Kind regards,</div>Charliemccayhttps://wiki.hl7.org/w/index.php?title=ITS_SIG_May_2008_WGM_agenda&diff=16547ITS SIG May 2008 WGM agenda2008-04-01T11:59:53Z<p>Charliemccay: </p>
<hr />
<div>The ITS SIG is meeting wed PM and thursday<br />
This is a placeholder for the detailed agenda</div>Charliemccayhttps://wiki.hl7.org/w/index.php?title=ITS_WG&diff=16546ITS WG2008-04-01T11:27:21Z<p>Charliemccay: /* WGMs */</p>
<hr />
<div>The XML SIG was renamed the ITS SIG in Jan 2007, wiki content from the XML SIG is found [[XML related issues | here]]. <br />
<br />
The ITS SIG supports the HL7 mission through the development of Implementable Technology Specifications and Messaging Protocol guidelines (e.g. ebXML, Webservices, MLLP, ..) to be used when putting the HL7 information specifications to use.<br />
<br />
Sponsoring TCs are [[Infrastructure and Messaging TC]] and [[Structured Documents TC]]<br />
<br />
==== Specifications maintained by the ITS SIG ====<br />
This is a first cut of the list - it needs to be updated with links to the balloted versions, and to any work in progress. I am also not convinced that it is complete. There is a list maintained in the INM section of the wiki of who is responsible for various documents [[INM_Work_Distribution#Implementable_Technology_Specifications_.28ITS_SIG.29]]<br />
<br />
* ebXML transport protocol<br />
* [[web services transport protocol]]<br />
* [[removable media transport protocol]]<br />
* MLLP transport protocol (R2, normative)<br />
* [[XML related issues|XML ITS (release 1)]]<br />
* v2 pipe-bar ITS sections in chapter 2<br />
* v2 XML ITS document<br />
* [[ITS possibilities not active]]<br />
<br />
==== ITS SIG Projects ====<br />
* [[ISO Datatypes]] -- this is part of the [[New ITS project]]<br />
* [[New ITS project]]<br />
* [[XML ITS Structures r1.1]]<br />
* Glossary Entry for [[ITS]]<br />
* [[ITS SIG action items]]<br />
* [[HSSP product review]]<br />
* [[web services release 2]] -- committee due<br />
* [[ebxml release 2]] -- membership <br />
* [[removable media]] -- committee due<br />
* [[xml its datatypes r2]] -- parked<br />
<br />
==== ITS SIG meetings ====<br />
===== Conference Calls =====<br />
* wednesday 4pm ITS SIG calls. Where there is no other agenda item, the ballot reconcilliation calls are recorded on the wiki page below<br />
** [[ITS SIG Recon Calls]] (attendance and dialin details)<br />
*[[ITS SIG telcon 20080305]]<br />
*[[ITS SIG telcon 20080130]]<br />
* wednesday 4pm Wednesday calls joint with INM for datatypes reconciliation<br />
*[[ITS SIG INM TC Datatypes recon calls]]<br />
* conference call scheduled for Mondays 12am every week<br />
*[[ITS SIG telcon 20070806]]<br />
*[[ITS SIG telcon 20070730]]<br />
*[[ITS SIG telcon 20070716]]<br />
*[[ITS SIG telcon 20070709]]<br />
*[[ITS SIG telcon 20070702]]<br />
* some calls with notes to be produced<br />
*[[ITS SIG telcon 20070702]]<br />
*[[ITS SIG telcon 20070514 agenda]] <br />
* Cologne WGM<br />
*[[ITS SIG telcon 20070328 agenda]] [[ITS SIG telcon 20070328 notes]] 7am eastern - next call<br />
*[[ITS SIG telcon 20070319 agenda]] [[ITS SIG telcon 20070319 notes]] 11am eastern <br />
*[[ITS SIG telcon 20070314 notes]] 7am eastern <br />
*[[ITS SIG telcon 20070305 notes]] 11am eastern <br />
*[[ITS SIG telcon 20070228 agenda]] [[ITS SIG telcon 20070228 notes]] no meeting - lack of quorum<br />
*[[ITS SIG telcon 20070226 agenda]]<br />
*[[ITS SIG telcon 20070219 notes]]<br />
*[[ITS SIG telcon 20070205 agenda]]<br />
*[[ITS SIG telcon 20070131 agenda]]<br />
*[[ITS SIG telcon 20070124 agenda]]<br />
<br />
===== WGMs =====<br />
*[[ITS SIG May 2008 WGM agenda]]<br />
*[[ITS SIG Sept 2007 WGM agenda]]<br />
*[[ITS SIG May 2007 WGM agenda]]<br />
*[[XML San Diego 2007 Agenda]]<br />
<br />
==== Admin ====<br />
* [[XML to ITS SIG changeover issues]]<br />
*[[ITS SIG co-chairs tasklist]]<br />
* [[XML related issues]] (previous content of this page has been moved here)<br />
<br />
==== May 2007 Ballot Preparation ====<br />
*[[http://www.hl7.org/documentcenter/public/schedules/Pubs_Schedule_2007.pdf ballot timetable]]<br />
*[[ITS 2007MAY advanced CBC]] -- announcement for ITS ballots in May<br />
* need intent to ballot document done by feb 11th http://www.hl7.org/Library/Committees/xml/ITS%5FSIG%5FNIB%5FMAY%5F2007%2Ezip package of Notification of intent to ballot documents -- submitted by email and accepted by Don Lloyd. The ebXML and removable media documents have been superseeded by documents submitted by Doug Pratt.<br />
* First draft content - 25th Feb<br />
* [[EbXML_C1_Ballot_Spreadsheet_with_proposed_resolutions]]<br />
<br />
{{SIG Category}}<br />
<br />
<br />
==== September 2007 Ballot Preparation ====<br />
* Draft XML ITS V3 Structures R1.1 [[http://www.hl7.org/Library/Committees/xml/xmlitsR1%2E1%2Ezip]] [[Draft Appendix: ITS R1.1 Extensibility Implementation Considerations]]<br />
* Draft New ITS specification [[http://www.hl7.org/Library/Committees/xml/NewITSSpecRelease1%2E1%2Ezip]]<br />
* Draft New ITS Guide [[http://www.hl7.org/Library/Committees/xml/NewITSGuide%2Exml]]</div>Charliemccayhttps://wiki.hl7.org/w/index.php?title=ITS_SIG_Recon_Calls&diff=16021ITS SIG Recon Calls2008-01-30T11:18:00Z<p>Charliemccay: </p>
<hr />
<div> Participation Information<br />
Phone Number: 702-894-2444<br />
Participant Passcode: 973164 <br />
Moderator Passcode: 5679 <br />
https://www.gotomeeting.com/join/272068753<br />
<br />
Call is scheduled for 1.0 hour <br />
Wed 04:00 PM (US Eastern Time, GMT -5)<br />
Please consult http://www.timeanddate.com/worldclock for your local times<br />
<br />
<br />
attendees:<br />
*20080123 - ISO datatypes reconciliation - no quorum</div>Charliemccayhttps://wiki.hl7.org/w/index.php?title=ITS_SIG_Recon_Calls&diff=16020ITS SIG Recon Calls2008-01-30T11:17:34Z<p>Charliemccay: </p>
<hr />
<div> Participation Information<br />
Phone Number: 702-894-2444<br />
Participant Passcode: 973164 <br />
Moderator Passcode: 5679 <br />
https://www.gotomeeting.com/join/272068753<br />
<br />
Call is scheduled for 1.0 hour <br />
Wed 04:00 PM (US Eastern Time, GMT -5)<br />
Please consult http://www.timeanddate.com/worldclock for your local times<br />
<br />
<br />
attendees:<br />
*20080123 - no quorum</div>Charliemccayhttps://wiki.hl7.org/w/index.php?title=ITS_SIG_telcon_20080130&diff=16019ITS SIG telcon 200801302008-01-30T11:14:24Z<p>Charliemccay: </p>
<hr />
<div> Participation Information<br />
Phone Number: 702-894-2444<br />
Participant Passcode: 973164 <br />
Moderator Passcode: 5679 <br />
https://www.gotomeeting.com/join/272068753<br />
<br />
Call is scheduled for 1.0 hour <br />
Wed 04:00 PM (US Eastern Time, GMT -5)<br />
Please consult http://www.timeanddate.com/worldclock for your local times<br />
<br />
<br />
* attendees<br />
* ITS SIG project scope statements review/revision<br />
* ITS SIG ballot planning<br />
* ITS SIG May WGM agenda planning<br />
* ISO datatypes reconciliation</div>Charliemccayhttps://wiki.hl7.org/w/index.php?title=ITS_SIG_Recon_Calls&diff=16018ITS SIG Recon Calls2008-01-30T11:12:10Z<p>Charliemccay: </p>
<hr />
<div> Participation Information<br />
Phone Number: 702-894-2444<br />
Participant Passcode: 973164 <br />
Moderator Passcode: 5679 <br />
https://www.gotomeeting.com/join/272068753<br />
<br />
Call is scheduled for 1.0 hour <br />
Wed 04:00 PM (US Eastern Time, GMT -5)<br />
Please consult http://www.timeanddate.com/worldclock for your local times<br />
<br />
<br />
attendees:</div>Charliemccayhttps://wiki.hl7.org/w/index.php?title=ITS_WG&diff=16017ITS WG2008-01-30T11:11:48Z<p>Charliemccay: /* Conference Calls */</p>
<hr />
<div>The XML SIG was renamed the ITS SIG in Jan 2007, wiki content from the XML SIG is found [[XML related issues | here]]. <br />
<br />
The ITS SIG supports the HL7 mission through the development of Implementable Technology Specifications and Messaging Protocol guidelines (e.g. ebXML, Webservices, MLLP, ..) to be used when putting the HL7 information specifications to use.<br />
<br />
Sponsoring TCs are [[Infrastructure and Messaging TC]] and [[Structured Documents TC]]<br />
<br />
==== Specifications maintained by the ITS SIG ====<br />
This is a first cut of the list - it needs to be updated with links to the balloted versions, and to any work in progress. I am also not convinced that it is complete. There is a list maintained in the INM section of the wiki of who is responsible for various documents [[INM_Work_Distribution#Implementable_Technology_Specifications_.28ITS_SIG.29]]<br />
<br />
* ebXML transport protocol<br />
* [[web services transport protocol]]<br />
* [[removable media transport protocol]]<br />
* MLLP transport protocol (R2, normative)<br />
* [[XML related issues|XML ITS (release 1)]]<br />
* v2 pipe-bar ITS sections in chapter 2<br />
* v2 XML ITS document<br />
* [[ITS possibilities not active]]<br />
<br />
==== ITS SIG Projects ====<br />
* [[ISO Datatypes]] -- this is part of the [[New ITS project]]<br />
* [[New ITS project]]<br />
* [[XML ITS Structures r1.1]]<br />
* Glossary Entry for [[ITS]]<br />
* [[ITS SIG action items]]<br />
* [[HSSP product review]]<br />
* [[web services release 2]] -- committee due<br />
* [[ebxml release 2]] -- membership <br />
* [[removable media]] -- committee due<br />
* [[xml its datatypes r2]] -- parked<br />
<br />
==== ITS SIG meetings ====<br />
===== Conference Calls =====<br />
* wednesday 4pm ITS SIG calls. Where there is no other agenda item, the ballot reconcilliation calls are recorded on the wiki page below<br />
** [[ITS SIG Recon Calls]] (attendance and dialin details)<br />
*[[ITS SIG telcon 20080130]]<br />
* wednesday 4pm Wednesday calls joint with INM for datatypes reconciliation<br />
*[[ITS SIG INM TC Datatypes recon calls]]<br />
* conference call scheduled for Mondays 12am every week<br />
*[[ITS SIG telcon 20070806]]<br />
*[[ITS SIG telcon 20070730]]<br />
*[[ITS SIG telcon 20070716]]<br />
*[[ITS SIG telcon 20070709]]<br />
*[[ITS SIG telcon 20070702]]<br />
* some calls with notes to be produced<br />
*[[ITS SIG telcon 20070702]]<br />
*[[ITS SIG telcon 20070514 agenda]] <br />
* Cologne WGM<br />
*[[ITS SIG telcon 20070328 agenda]] [[ITS SIG telcon 20070328 notes]] 7am eastern - next call<br />
*[[ITS SIG telcon 20070319 agenda]] [[ITS SIG telcon 20070319 notes]] 11am eastern <br />
*[[ITS SIG telcon 20070314 notes]] 7am eastern <br />
*[[ITS SIG telcon 20070305 notes]] 11am eastern <br />
*[[ITS SIG telcon 20070228 agenda]] [[ITS SIG telcon 20070228 notes]] no meeting - lack of quorum<br />
*[[ITS SIG telcon 20070226 agenda]]<br />
*[[ITS SIG telcon 20070219 notes]]<br />
*[[ITS SIG telcon 20070205 agenda]]<br />
*[[ITS SIG telcon 20070131 agenda]]<br />
*[[ITS SIG telcon 20070124 agenda]]<br />
<br />
===== WGMs =====<br />
*[[ITS SIG Sept 2007 WGM agenda]]<br />
*[[ITS SIG May 2007 WGM agenda]]<br />
*[[XML San Diego 2007 Agenda]]<br />
<br />
==== Admin ====<br />
* [[XML to ITS SIG changeover issues]]<br />
*[[ITS SIG co-chairs tasklist]]<br />
* [[XML related issues]] (previous content of this page has been moved here)<br />
<br />
==== May 2007 Ballot Preparation ====<br />
*[[http://www.hl7.org/documentcenter/public/schedules/Pubs_Schedule_2007.pdf ballot timetable]]<br />
*[[ITS 2007MAY advanced CBC]] -- announcement for ITS ballots in May<br />
* need intent to ballot document done by feb 11th http://www.hl7.org/Library/Committees/xml/ITS%5FSIG%5FNIB%5FMAY%5F2007%2Ezip package of Notification of intent to ballot documents -- submitted by email and accepted by Don Lloyd. The ebXML and removable media documents have been superseeded by documents submitted by Doug Pratt.<br />
* First draft content - 25th Feb<br />
* [[EbXML_C1_Ballot_Spreadsheet_with_proposed_resolutions]]<br />
<br />
{{SIG Category}}<br />
<br />
<br />
==== September 2007 Ballot Preparation ====<br />
* Draft XML ITS V3 Structures R1.1 [[http://www.hl7.org/Library/Committees/xml/xmlitsR1%2E1%2Ezip]] [[Draft Appendix: ITS R1.1 Extensibility Implementation Considerations]]<br />
* Draft New ITS specification [[http://www.hl7.org/Library/Committees/xml/NewITSSpecRelease1%2E1%2Ezip]]<br />
* Draft New ITS Guide [[http://www.hl7.org/Library/Committees/xml/NewITSGuide%2Exml]]</div>Charliemccayhttps://wiki.hl7.org/w/index.php?title=ITS_WG&diff=16016ITS WG2008-01-30T11:05:48Z<p>Charliemccay: /* ITS SIG Projects */</p>
<hr />
<div>The XML SIG was renamed the ITS SIG in Jan 2007, wiki content from the XML SIG is found [[XML related issues | here]]. <br />
<br />
The ITS SIG supports the HL7 mission through the development of Implementable Technology Specifications and Messaging Protocol guidelines (e.g. ebXML, Webservices, MLLP, ..) to be used when putting the HL7 information specifications to use.<br />
<br />
Sponsoring TCs are [[Infrastructure and Messaging TC]] and [[Structured Documents TC]]<br />
<br />
==== Specifications maintained by the ITS SIG ====<br />
This is a first cut of the list - it needs to be updated with links to the balloted versions, and to any work in progress. I am also not convinced that it is complete. There is a list maintained in the INM section of the wiki of who is responsible for various documents [[INM_Work_Distribution#Implementable_Technology_Specifications_.28ITS_SIG.29]]<br />
<br />
* ebXML transport protocol<br />
* [[web services transport protocol]]<br />
* [[removable media transport protocol]]<br />
* MLLP transport protocol (R2, normative)<br />
* [[XML related issues|XML ITS (release 1)]]<br />
* v2 pipe-bar ITS sections in chapter 2<br />
* v2 XML ITS document<br />
* [[ITS possibilities not active]]<br />
<br />
==== ITS SIG Projects ====<br />
* [[ISO Datatypes]] -- this is part of the [[New ITS project]]<br />
* [[New ITS project]]<br />
* [[XML ITS Structures r1.1]]<br />
* Glossary Entry for [[ITS]]<br />
* [[ITS SIG action items]]<br />
* [[HSSP product review]]<br />
* [[web services release 2]] -- committee due<br />
* [[ebxml release 2]] -- membership <br />
* [[removable media]] -- committee due<br />
* [[xml its datatypes r2]] -- parked<br />
<br />
==== ITS SIG meetings ====<br />
===== Conference Calls =====<br />
* wednesday 4pm Wednesday calls joint with INM for datatypes reconciliation<br />
*[[ITS SIG INM TC Datatypes recon calls]]<br />
* conference call scheduled for Mondays 12am every week<br />
*[[ITS SIG telcon 20070806]]<br />
*[[ITS SIG telcon 20070730]]<br />
*[[ITS SIG telcon 20070716]]<br />
*[[ITS SIG telcon 20070709]]<br />
*[[ITS SIG telcon 20070702]]<br />
* some calls with notes to be produced<br />
*[[ITS SIG telcon 20070702]]<br />
*[[ITS SIG telcon 20070514 agenda]] <br />
* Cologne WGM<br />
*[[ITS SIG telcon 20070328 agenda]] [[ITS SIG telcon 20070328 notes]] 7am eastern - next call<br />
*[[ITS SIG telcon 20070319 agenda]] [[ITS SIG telcon 20070319 notes]] 11am eastern <br />
*[[ITS SIG telcon 20070314 notes]] 7am eastern <br />
*[[ITS SIG telcon 20070305 notes]] 11am eastern <br />
*[[ITS SIG telcon 20070228 agenda]] [[ITS SIG telcon 20070228 notes]] no meeting - lack of quorum<br />
*[[ITS SIG telcon 20070226 agenda]]<br />
*[[ITS SIG telcon 20070219 notes]]<br />
*[[ITS SIG telcon 20070205 agenda]]<br />
*[[ITS SIG telcon 20070131 agenda]]<br />
*[[ITS SIG telcon 20070124 agenda]]<br />
<br />
===== WGMs =====<br />
*[[ITS SIG Sept 2007 WGM agenda]]<br />
*[[ITS SIG May 2007 WGM agenda]]<br />
*[[XML San Diego 2007 Agenda]]<br />
<br />
==== Admin ====<br />
* [[XML to ITS SIG changeover issues]]<br />
*[[ITS SIG co-chairs tasklist]]<br />
* [[XML related issues]] (previous content of this page has been moved here)<br />
<br />
==== May 2007 Ballot Preparation ====<br />
*[[http://www.hl7.org/documentcenter/public/schedules/Pubs_Schedule_2007.pdf ballot timetable]]<br />
*[[ITS 2007MAY advanced CBC]] -- announcement for ITS ballots in May<br />
* need intent to ballot document done by feb 11th http://www.hl7.org/Library/Committees/xml/ITS%5FSIG%5FNIB%5FMAY%5F2007%2Ezip package of Notification of intent to ballot documents -- submitted by email and accepted by Don Lloyd. The ebXML and removable media documents have been superseeded by documents submitted by Doug Pratt.<br />
* First draft content - 25th Feb<br />
* [[EbXML_C1_Ballot_Spreadsheet_with_proposed_resolutions]]<br />
<br />
{{SIG Category}}<br />
<br />
<br />
==== September 2007 Ballot Preparation ====<br />
* Draft XML ITS V3 Structures R1.1 [[http://www.hl7.org/Library/Committees/xml/xmlitsR1%2E1%2Ezip]] [[Draft Appendix: ITS R1.1 Extensibility Implementation Considerations]]<br />
* Draft New ITS specification [[http://www.hl7.org/Library/Committees/xml/NewITSSpecRelease1%2E1%2Ezip]]<br />
* Draft New ITS Guide [[http://www.hl7.org/Library/Committees/xml/NewITSGuide%2Exml]]</div>Charliemccayhttps://wiki.hl7.org/w/index.php?title=ITS_WG&diff=16015ITS WG2008-01-30T11:04:51Z<p>Charliemccay: /* ITS SIG Projects */</p>
<hr />
<div>The XML SIG was renamed the ITS SIG in Jan 2007, wiki content from the XML SIG is found [[XML related issues | here]]. <br />
<br />
The ITS SIG supports the HL7 mission through the development of Implementable Technology Specifications and Messaging Protocol guidelines (e.g. ebXML, Webservices, MLLP, ..) to be used when putting the HL7 information specifications to use.<br />
<br />
Sponsoring TCs are [[Infrastructure and Messaging TC]] and [[Structured Documents TC]]<br />
<br />
==== Specifications maintained by the ITS SIG ====<br />
This is a first cut of the list - it needs to be updated with links to the balloted versions, and to any work in progress. I am also not convinced that it is complete. There is a list maintained in the INM section of the wiki of who is responsible for various documents [[INM_Work_Distribution#Implementable_Technology_Specifications_.28ITS_SIG.29]]<br />
<br />
* ebXML transport protocol<br />
* [[web services transport protocol]]<br />
* [[removable media transport protocol]]<br />
* MLLP transport protocol (R2, normative)<br />
* [[XML related issues|XML ITS (release 1)]]<br />
* v2 pipe-bar ITS sections in chapter 2<br />
* v2 XML ITS document<br />
* [[ITS possibilities not active]]<br />
<br />
==== ITS SIG Projects ====<br />
* [[ISO Datatypes]] -- this is part of the New ITS project<br />
* [[New ITS project]]<br />
* [[XML ITS Structures r1.1]]<br />
* Glossary Entry for [[ITS]]<br />
* [[ITS SIG action items]]<br />
* [[HSSP product review]]<br />
* [[web services release 2]] -- committee due<br />
* [[ebxml release 2]] -- membership <br />
* [[removable media]] -- committee due<br />
* [[xml its datatypes r2]] -- parked<br />
<br />
==== ITS SIG meetings ====<br />
===== Conference Calls =====<br />
* wednesday 4pm Wednesday calls joint with INM for datatypes reconciliation<br />
*[[ITS SIG INM TC Datatypes recon calls]]<br />
* conference call scheduled for Mondays 12am every week<br />
*[[ITS SIG telcon 20070806]]<br />
*[[ITS SIG telcon 20070730]]<br />
*[[ITS SIG telcon 20070716]]<br />
*[[ITS SIG telcon 20070709]]<br />
*[[ITS SIG telcon 20070702]]<br />
* some calls with notes to be produced<br />
*[[ITS SIG telcon 20070702]]<br />
*[[ITS SIG telcon 20070514 agenda]] <br />
* Cologne WGM<br />
*[[ITS SIG telcon 20070328 agenda]] [[ITS SIG telcon 20070328 notes]] 7am eastern - next call<br />
*[[ITS SIG telcon 20070319 agenda]] [[ITS SIG telcon 20070319 notes]] 11am eastern <br />
*[[ITS SIG telcon 20070314 notes]] 7am eastern <br />
*[[ITS SIG telcon 20070305 notes]] 11am eastern <br />
*[[ITS SIG telcon 20070228 agenda]] [[ITS SIG telcon 20070228 notes]] no meeting - lack of quorum<br />
*[[ITS SIG telcon 20070226 agenda]]<br />
*[[ITS SIG telcon 20070219 notes]]<br />
*[[ITS SIG telcon 20070205 agenda]]<br />
*[[ITS SIG telcon 20070131 agenda]]<br />
*[[ITS SIG telcon 20070124 agenda]]<br />
<br />
===== WGMs =====<br />
*[[ITS SIG Sept 2007 WGM agenda]]<br />
*[[ITS SIG May 2007 WGM agenda]]<br />
*[[XML San Diego 2007 Agenda]]<br />
<br />
==== Admin ====<br />
* [[XML to ITS SIG changeover issues]]<br />
*[[ITS SIG co-chairs tasklist]]<br />
* [[XML related issues]] (previous content of this page has been moved here)<br />
<br />
==== May 2007 Ballot Preparation ====<br />
*[[http://www.hl7.org/documentcenter/public/schedules/Pubs_Schedule_2007.pdf ballot timetable]]<br />
*[[ITS 2007MAY advanced CBC]] -- announcement for ITS ballots in May<br />
* need intent to ballot document done by feb 11th http://www.hl7.org/Library/Committees/xml/ITS%5FSIG%5FNIB%5FMAY%5F2007%2Ezip package of Notification of intent to ballot documents -- submitted by email and accepted by Don Lloyd. The ebXML and removable media documents have been superseeded by documents submitted by Doug Pratt.<br />
* First draft content - 25th Feb<br />
* [[EbXML_C1_Ballot_Spreadsheet_with_proposed_resolutions]]<br />
<br />
{{SIG Category}}<br />
<br />
<br />
==== September 2007 Ballot Preparation ====<br />
* Draft XML ITS V3 Structures R1.1 [[http://www.hl7.org/Library/Committees/xml/xmlitsR1%2E1%2Ezip]] [[Draft Appendix: ITS R1.1 Extensibility Implementation Considerations]]<br />
* Draft New ITS specification [[http://www.hl7.org/Library/Committees/xml/NewITSSpecRelease1%2E1%2Ezip]]<br />
* Draft New ITS Guide [[http://www.hl7.org/Library/Committees/xml/NewITSGuide%2Exml]]</div>Charliemccayhttps://wiki.hl7.org/w/index.php?title=ISO_Datatypes&diff=15992ISO Datatypes2008-01-29T14:49:25Z<p>Charliemccay: </p>
<hr />
<div>This is a project under the [[CEN ISO HL7 Joint Initiative]]<br />
<br />
This is a project page for the ISO datatypes activity led by Grahame Greive for HL7, and Tom Marley for ISO.<br />
<br />
The project is currently in reconciliation activity -- with the work being done on the XML SIG telcons [[XML SIG#Conference_Calls]].<br />
<br />
Note: this page was a full draft of the ISO datatypes document - this is now maintained in the hl7 svn repository, and published in the Ballot pack [http://www.hl7.org/v3ballot/html/infrastructure/its_r2/isodatatypes.htm].</div>Charliemccay