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

Structured Document Template Design Pilot

From HL7Wiki
Revision as of 17:42, 5 February 2010 by Janecurry (talk | contribs)
Jump to navigation Jump to search

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 through publication of the implementation guide and associated technical artifacts, including architectural integration points used for implementation.

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 Process

  • Weekly telecon Fridays at 12pmE using Tooling's telecon +1 770-657-9270; Participant PassCode: 946251#
  • Project plan to be provided Feb 5th
  • Each Sub-Project maintains current status on their respective wiki page and the teleconference will review and address any issues
  • Standing Agenda Items
    • Review of project plan and tasks
    • Opportunity to ask questions and answers

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.
- Determine the extent to which the tools can demonstrate traceability from requirements through to implementation artifacts.
- Maintain liaison with the Templates Registry Pilot to share learnings
  • Deliverables
    • Sample CDA IG(s) based on the tools (see zip file@ http://gforge.hl7.org/gf/project/templatesreg/docman/?subdir=127)
    • 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)
    • Summary of "architectural integration" points (e.g. a description of artifacts and connection points among tools that can be used to facilitate implementation).
    • Final report regarding how tool / tool combinations stacked up against requirements.

Test case

  • Build a CDA R2 Tuberculosis follow up progress note, end to end (from requirements to final publication).
    • CDA R2 Tuberculosis follow up progress note (templateID "2.16.840.1.113883.10.20.15.2.6.1.1.1.1.1.2.3") SHALL contain 1..1 TB Results Section (templateId "2.16.840.1.113883.10.20.15.2.6");
      • there can be any number of patient names, but at least one of them must include a given and family name.
      • TB Results Section (templateId "2.16.840.1.113883.10.20.15.2.6"):
        • CONFORMS TO CCD Results Section (templateId: 2.16.840.1.113883.10.20.1.14);
        • SHALL contain [1..1] code/@code="30954-2" Relevant diagnostic tests and/or laboratory data (CodeSystem: 2.16.840.1.113883.6.1 LOINC) STATIC;
        • SHALL contain [1..1] title="Relevant diagnostic tests and/or laboratory data";
        • SHALL contain [1..1] text
        • MAY contain [0..*] TB Result organizer (templateId "2.16.840.1.113883.10.20.15.3.21");
        • MAY contain [0..*] TB Result observation(templateId "2.16.840.1.113883.10.20.15.3.13");
      • TB Result organizer (templateId "2.16.840.1.113883.10.20.15.3.21"):
        • CONFORMS TO CCD Result Organizer (templateId "2.16.840.1.113883.10.20.1.32");
        • SHALL contain 1..1 code/@code, which SHALL be selected from ValueSet 2.16.840.1.114222.4.11.3205 Lab Test Result Name (TB) DYNAMIC
        • SHALL contain 1..1 TB Result observation (templateId 2.16.840.1.113883.10.20.15.3.13");
      • TB Result observation(templateId 2.16.840.1.113883.10.20.15.3.13");
        • CONFORMS TO CCD Result Observation(templateId "2.16.840.1.113883.10.20.1.31");
        • classCode SHALL be "OBS";
        • SHALL contain 1..1 code/@code, which SHALL be selected from ValueSet 2.16.840.1.114222.4.11.3205 Lab Test Result Name (TB) DYNAMIC
        • SHALL contain 1..1 statusCode/@code="completed" (CodeSystem: 2.16.840.1.113883.5.14 HL7ActStatus) STATIC


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;
    • Lyssa Neel pneel@infoway-inforoute.ca;
    • 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

Sub-Projects

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