This wiki has undergone a migration to Confluence found Here

Difference between revisions of "Structured Document Template Design Pilot"

From HL7Wiki
Jump to navigation Jump to search
Line 30: Line 30:
 
***narrative (no entries defined)
 
***narrative (no entries defined)
 
**vital signs section
 
**vital signs section
***blood pressure organizer with component BP observations
+
***blood pressure organizer [inherits from CCD Result Organizer] with component BP observations [inherits from CCD Result Observation]
 +
****BP organizer specialization includes value set binding to SNOMED CT.
 +
****BP observations include single code bindings to SNOMED CT.
 
***heart rate observation
 
***heart rate observation
 
**encounter diagnosis section
 
**encounter diagnosis section

Revision as of 16:31, 17 December 2009

Structure Document Template Design Pilot

Project scope

  • objectives: Test evolving CDA template tooling against tooling committee requirements and SDWG Implementation Guide production process via a small project.
  • scope: [1] Test functionality of tools as they currently exist;[2] Produce a (mock, small) CDA IG using the participant tools

The Structured Documents Working Group, together with developers of the OHT MDHT CDA tools [1], the OHT NHS Static Model Designer [2], and the Mitre tools, will work through an end to end development of a small mock CDA R2 Implementation Guide. The end to end process will span from templates development all the way to publication of the implementation guide and associated technical artifacts.

Out of scope is the introduction of new functionality not currently available in the existing tools. The project is focused on a rapid assessment of the current state of the tools, either working singularly or together, and the identification of gaps and suggestions for subsequent tooling enhancements.

Project objectives and deliverables

  • Objectives
- Compare tools against requirements to determine gaps.
- Develop suggestions for tooling enhancements.
- Determine if there are optimal overlaps of tools that better achieve the requirements than any single tool alone.
  • Deliverables
    • Sample CDA IG(s) based on the tools
    • Sample CDA IG, built "the old-fashioned way" (as a comparison baseline)
    • Summary of steps used to create sample CDA IG(s)
      • Comparison against requirements
      • Manual steps needed
      • Quantitative measures (e.g. hours to produce)
    • Final report regarding how tool / tool combinations stacked up against requirements

Test case

  • Build a CDA R2 progress note, end to end (from requirements to final publication).
  • This will be a very small implementation guide. Potential components include:
    • HPI section
      • narrative (no entries defined)
    • vital signs section
      • blood pressure organizer [inherits from CCD Result Organizer] with component BP observations [inherits from CCD Result Observation]
        • BP organizer specialization includes value set binding to SNOMED CT.
        • BP observations include single code bindings to SNOMED CT.
      • heart rate observation
    • encounter diagnosis section
      • encounter diagnosis entry


Participants

  • Primary Sponsor/Work Group: Structured Documents Work Group
  • Co-sponsor Work Group(s): Templates, Tooling
  • Project facilitator: Bob Dolin BobDolin@gmail.com
  • Other interested parties
    • Dave Carlson dcarlson@xmlmodeling.com;
    • John Timm johntimm@us.ibm.com;
    • Ravi Natarajan ravi.natarajan@nhs.net;
    • Townend Ian ian.townend@nhs.net;
    • Andy Gregorowicz andy@mitre.org;
    • Austin Kreisler austin.j.kreisler@saic.com;
  • Modeling facilitator: Bob Dolin BobDolin@gmail.com
  • Publishing facilitator:Peter Gilbert PeterNGilbert@gmail.com
  • Vocabulary facilitator: n/a
  • Domain expert rep: n/a
  • Data Analyst facilitator: n/a
  • Business requirement analyst
    • Keith Boone keith.boone@ge.com;
    • Liora Alschuler liora@alschulerassociates.com
  • Requirements process facilitator
    • Jane Curry janecurry@healthinfostrategies.com;
    • Mark Shafarman mark.shafarman@earthlink.net