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

Difference between revisions of "PC CIMI Proof of Concept"

From HL7Wiki
Jump to navigation Jump to search
 
(20 intermediate revisions by the same user not shown)
Line 5: Line 5:
 
Return to [[CIMI]]
 
Return to [[CIMI]]
  
−
<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>
+
==Project Information==
  
−
==Project Information==
+
[[Media: HL7_Project_Scope_Statement_v2015.1_CIMI_POC.docx | Scope Statement]]
  
−
Link to [http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm Project Insight Searchable Database] Entry, which contains:
+
[http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=1253 Project Insight]
−
*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
 
  
 +
Use existing PC-defined clinical requirements to create a set of CIMI observation result models with semantic tags appropriate for automated classification. This exercise will
 +
* Demonstrate CIMI capability & identify additional requirements for CIMI from PC perspective
 +
* Demonstrate how DAMs may be compositionally related to DCMs & identify gaps in HL7 development framework
 +
* Demonstrate relationship between information models and logically computable expressions
  
−
==Meeting Information==
+
The content scope will be drawn primarily from the skin assessment DAM, but it may be augmented to demonstrate critical requirements such as negation. It may further phase the analysis to ensure key patterns (lab test, vital sign, assessment instrument) can be represented before addressing the question of how large numbers of these clinical statements are assembled into compositions.
−
*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
 
  
 +
A related project may implement these models in a specification generation tool (such as MDHT, Art Décor, or a FHIR server), generate a specification, implement the specification in software, & test. These steps are not in scope for this investigative project scope statement.
  
−
==Status==
+
==Meeting Information==
−
*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]
+
*Link to call [http://www.hl7.org/concalls/CallDetails.aspx?concall=30326 project meeting schedule]
−
*If in DSTU, link to [http://www.hl7.org/dstucomments/ DSTU comments page]
+
*[[PC CIMI POC Minutes|Minutes ]]
−
*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
 
  
 +
==Plan==
 +
* Confirm scope: in process
 +
**phase 1 scope (suggestion)
 +
***coded observation (skin condition)
 +
***quantitative observation (BMI)
 +
***assessment (Braden)
 +
***negation (device?)
 +
* Confirm output targets
 +
* Confirm tooling
 +
* Draft first iteration (test each type of statement)
 +
* Refine
 +
* Draft second iteration (full use case)
 +
* Refine
 +
* Provide feedback to CIMI & PC
  
 
==Issues/Hot Topics==
 
==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])
+
# Use of LOINC & SNOMED CT
−
 
+
# Model binding approach for output formats (e.g., FHIR)
 +
# How to address composition
 +
# Immature observable model
  
 
==Project Documents==
 
==Project Documents==
−
*Link to working documents/[[Main_Page|wiki pages]]
+
*[http://fhims.org/press_ulcer.html Skin Risk Model]
−
*Link to [http://gforge.hl7.org/gf/project/ project GForge]
+
*[[Media:CIMIConcentricSemantics.pptx | Semantics]]
−
*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
+
*[[Media:Candidate_Approach_for_Semantic_Binding.pptx | Semantics 2]]
−
 
+
*[[Media:Observation_patterns_170521.pptx | Semantics 3]]
 +
*[[Media:ExaminationRequirements.xlsx | Requirements for exam pattern]]
  
 
<noinclude>==Categorization== </noinclude>
 
<noinclude>==Categorization== </noinclude>
−
To include your Project Page in a category listing, just include a statement like <nowiki>[[Category:Active_Projects]]</nowiki>
+
<nowiki>[[Category:Active_Projects]]</nowiki>
−
  [[Category:StyleGuides]]
 

Latest revision as of 23:46, 23 May 2017


Return to Patient Care

Return to CIMI

Project Information

Scope Statement

Project Insight

Use existing PC-defined clinical requirements to create a set of CIMI observation result models with semantic tags appropriate for automated classification. This exercise will

  • Demonstrate CIMI capability & identify additional requirements for CIMI from PC perspective
  • Demonstrate how DAMs may be compositionally related to DCMs & identify gaps in HL7 development framework
  • Demonstrate relationship between information models and logically computable expressions

The content scope will be drawn primarily from the skin assessment DAM, but it may be augmented to demonstrate critical requirements such as negation. It may further phase the analysis to ensure key patterns (lab test, vital sign, assessment instrument) can be represented before addressing the question of how large numbers of these clinical statements are assembled into compositions.

A related project may implement these models in a specification generation tool (such as MDHT, Art Décor, or a FHIR server), generate a specification, implement the specification in software, & test. These steps are not in scope for this investigative project scope statement.

Meeting Information

Plan

  • Confirm scope: in process
    • phase 1 scope (suggestion)
      • coded observation (skin condition)
      • quantitative observation (BMI)
      • assessment (Braden)
      • negation (device?)
  • Confirm output targets
  • Confirm tooling
  • Draft first iteration (test each type of statement)
  • Refine
  • Draft second iteration (full use case)
  • Refine
  • Provide feedback to CIMI & PC

Issues/Hot Topics

  1. Use of LOINC & SNOMED CT
  2. Model binding approach for output formats (e.g., FHIR)
  3. How to address composition
  4. Immature observable model

Project Documents

Categorization

[[Category:Active_Projects]]

Retrieved from "https://wiki.hl7.org/w/index.php?title=PC_CIMI_Proof_of_Concept&oldid=139825"