This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "Detailed Clinical Model project"

From HL7Wiki
Jump to navigation Jump to search
 
(56 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
[[Category:Patient Care]]
 
[[Category:Patient Care]]
 
[[Category:Templates]]
 
[[Category:Templates]]
 +
[[Category:Patient Care Active Project]]
 
[[Category:Detailed Clinical Models]]
 
[[Category:Detailed Clinical Models]]
 +
__NOTOC__
 +
This is the project page for the new Detailed Clinical Models projects sponsored by [[Patient Care]] WG.  The [[Previous_DCM_project | previous Detailed Clinical Models project]] previous DCM project page is available for reference.
  
return to: [[Patient Care]]
+
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''
 +
*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]
  
further to: [[Detailed Clinical Models]]
+
<noinclude>''This template was developed using examples from other project pagess: Annotated ECG, BRIDG as DAM, Canonical Pedigree, DCM for Dev, EHR Interop, EHR RM-ES, Oncology EHR, RPS, Templates registry, SPL, VMR </noinclude>
  
further to: [[Detailed Clinical Model instance construction]]
+
==Project Information==
  
further to: [[Detailed Clinical Model guidelines for creation]]  
+
Link to [http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm Project Insight Searchable Database] Entry, which contains:
 +
*Brief description of project
 +
*Name the project facilitators, (add contact info if desired)
 +
*Link to project scope statement
 +
*Name the [http://www.hl7.org/listservice/index.cfm? project listserv] if a special one exists
  
further to: [[DAM vs DCM vs SAEAF]]
 
  
further to: [[Governance]]
+
==Meeting Information==
 +
*link to or list [http://www.hl7.org/concalls/index.cfm?action=home.welcome& project meeting schedule]
 +
*[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
  
  
=Introduction=
+
==Status==
 +
*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]
 +
*If in DSTU, link to [http://www.hl7.org/dstucomments/ DSTU comments page]
 +
*If in development, link to [http://gforge.hl7.org/gf/project/work in progress]
 +
*Some projects explicitly list objectives from scope statement and status for each
  
  
The DCM series of projects are as such a follow up of the DCM meeting in Boca Raton, led by Craig Parker and the DCM Brisbane workshop in 2007 with CEN, ISO, HL7, OpenEHR and clinical involvement where the recommendations were to work on harmonization of granular and detailed clinical content and where four action areas included clinician involvement, quality of detailed clinical models, representation formalisms and establishing and maintaining repositories. This is because different communities where working in splendid isolation on the same specifications of blood pressure, pulse, breathing, Apgar score, Glasgow Coma Scale, Health and Physical, assessments and so on.  
+
==Issues/Hot Topics==
 +
*List issues or link to issues tracking repository ([[Template:NEW_V3_Publishing_Issue|wiki pages]] or [http://gforge.hl7.org/gf/project/ GForge])
  
=Project scope=
 
  
The overall goals of the DCM initiative are:
+
==Project Documents==
 +
*Link to working documents/[[Main_Page|wiki pages]]
 +
*Link to [http://gforge.hl7.org/gf/project/ project GForge]
 +
*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
  
* to develop methods, tools for requirements gathering with clinicians, requirements for modelling tools,
 
* to enforce quality control, authorisation and governance of DCM rules
 
* to identify clinical items, binding of clinical content to terminology,
 
* to model generically and make transforms to different formalisms,
 
 
and
 
 
* to maintain in a repository a set of DCM that are useable in different standards, formats and different technical implementations using the same generic model. The purpose is to enhance the semantic interoperability between different systems and developments.
 
 
  
Based on discussions in ISO Joint Working Group 9, the JWG leadership requested two projects to be started:  
+
[[Category:Active_Projects]]
 
+
  [[Category:StyleGuides]]
1. A set of examples, useful in a standard
 
2. A set of criteria for good quality of DCM that are indeed clinically sound and implementable in different technical environments.
 
 
 
 
We have created a Top 10 list of DCMs and discussed its use in HL7 project 320 on DCM, where this document is an update of.  Establishing DCM criteria and methodologies is currently done under ISO NIWP 13972, which was approved on July 2009.
 
 
 
This proposal includes the proper representation of assessment scales, indexes and scoring systems. It will use elements of other HL7 WGs or projects such as Terminfo, Structured Documents, Templates and Clinical Statement. A DCM includes the purpose of one or small set of clinical data elements, the evidence base, data element specification, proper procedure, interpretation of values, and literature references. A guideline for this has been created on behalf of Nictiz in the Netherlands.
 
 
 
 
A DCM specification must be
 
* usable within the HL7 Clinical Statement and HL7 template specification
 
* meet HL7 terminfo requirements
 
* adjustable to the CEN/IOS 13606 and OpenEHR archetype environment, and the Clinical template specification, among others.
 
 
 
 
Technical implementations that would be able to deploy DCM include GUI design, database design, HL7 message design, algorithm design, rule-based Decision Support System design, among others. In particular a DCM is to form a bridge between different technical representation formats, in particular HL7 v3 templates / clinical statements and OpenEHR archetypes. That is the harmonization aspect of DCM. In order to actually use a DCM, the transformation to HL7 must be made. This is done via mapping the DCM content to a Clinical Statement R-MIM, in any HL7 domain that uses Clinical Statement. The formalism to use a DCM in HL7 space would be that of an HL7 v3 template.
 
 
 
=Action items=
 
 
 
 
 
=Project process=
 
 
 
 
 
=Project objectives and deliverables=
 
 
 
 
 
=Links to relevant documents=
 
 
 
 
 
=Participants=
 
 
 
==DCM Users==
 
 
 
==DCM Annonators==
 
 
 
==DCM Liasons==
 
 
 
==DCM Developer==
 
 
 
==DCM Contriutors==
 
 
 
 
 
=Sub Projects=
 

Latest revision as of 09:53, 25 May 2013


This is the project page for the new Detailed Clinical Models projects sponsored by Patient Care WG. The previous Detailed Clinical Models project previous DCM project page is available for reference.

Return to Main Page - include link to return to Work Group main page or wiki page who sponsored the project

This template was developed using examples from other project pagess: Annotated ECG, BRIDG as DAM, Canonical Pedigree, DCM for Dev, EHR Interop, EHR RM-ES, Oncology EHR, RPS, Templates registry, SPL, VMR

Project Information

Link to Project Insight Searchable Database Entry, which contains:

  • Brief description of project
  • Name the project facilitators, (add contact info if desired)
  • Link to project scope statement
  • Name the project listserv if a special one exists


Meeting Information


Status

  • If balloting, list ballot name/cycle/link
  • If in DSTU, link to DSTU comments page
  • If in development, link to in progress
  • Some projects explicitly list objectives from scope statement and status for each


Issues/Hot Topics


Project Documents