Project Page for Electronic Case Reporting
Contents
Project Page for Electronic Case Reporting
Return to Public Health and Emergency Response - HL7 web site
Return to [PHER main page - HL7 wiki]
- Project co-sponsors
Project Information
Links to previous efforts / Background material
Link to project scope statement
PSS for Electronic Case Reporting
Name the project facilitators
- Project facilitator (1 Mandatory) Maribeth Gagnon (CDC)
- Other interested parties and their roles John Roberts (PHER co-chair, Tennessee Department of Health)
- John Loonsk (Executive Sponsor, CGI Federal)
- Multi-disciplinary project team (recommended)
** Modeling facilitators - Eric Haas (Contractor to APHL), AbdulMalik Shakir (Contractor) ** Publishing facilitator - Jean Duteau (Hl7 Canada) ** Vocabulary facilitator - Riki Merrick (Contractor to APHL) ** Domain expert rep - Erin Holt Coyne (Tennessee Department of Health) ** Business requirement analyst - TBD ** Conformance facilitator (for IG projects) - TBD
Status and Timeline
PSS - Oct 18th Writing assignments are due 10/31 Goal to have a Final draft 11/17 last day for submission for Ballto Nove 28th?
Assignments:
- Purpose – John Loonsk and John Roberts
- Background -- John Loonsk and John Roberts
- Scope -- John Loonsk and John Roberts
- Future work -- John Roberts
- Audience- MariBeth to pull existing information from PHRI
- Approach (use case, actors, processes, data flows swim lanes diagrams, interaction diagrams, etc. -- Laura Conn and Shu McGarvey
- List of templates generated from Trifolia/authoring tool -- Eric Haas
- Appendices (templates, value sets)-- Eric Haas
Draft Introductory Material
NOTE: the IG is split into 2 parts an introductino and a templates part.
Status: draft
Status date: 20151102
Draft version of IG Part-1:eICR C-CDA IG Intro
Document: eICR C-CDA IG Intro
Consolidated Comments: eICR C-CDA IG Intro Comments Table
Link to templates library
To see template detail click on the link below, navigate to "Templates" tab and select 'PHCR" in the left menu bar. Art Decor provides am HTML table view of the constraints and description of the cda document tempates. If you would like to contribute to authoring the templates, DEs, vocabulary contact Eric Haas
Issues list and Implications reusing CCDA templates
- Extra stuff we are adding to the base US Realm header and the extra stuff CCDA requires in both US Realm Header and Section and Entry templates summary below
Implications reusing CCDA templates
- Here is a summary of the cCDA template issues – a lot of these will be cleare when we understand what "R" and "RE" means in eICR DEs list
- eICR required elements not present in C-CDA:
- Entry template required in EiCR but 0..1 (MAY) in CCDA eg ServiceDeliveryLocation, Indication, Encounter Diagnosis in Encounter Activity and Pregnancy and Social History Observation entry templates in Social History section - implication is won't know why information is missing ( unknown, or ignored) - if want to require then need to constrain these templates.
- C-CDA required elements not required by eICR:
- Custodian is required in document header - who is the custodian / Sender (Provider Org) , intermediary (PHCP) or Receiver ( PHA )?
- C-CDA incompatible with eICR constraints:
- nullflavor allowed for several eICR Required elements at section level ( Results Section, Problem Section, Medications Section, Encounters Section ) Note that is probably compatible with our definition of required but need to bring up if required means no null flavors ( i.e. Mandatory )
- How to document constraints for occupation hx or only diagnosis and symptoms without constraining template or valueset?
- How to indicate Patient is not pregnant. Currently in ccda only assert pregnancy
- option 1 - use constrained pregnancy template with negation indicator if asserting not Pregnant, and nullflavoe if unknown or Not applicable (too young, old or male)
- option 2 - use problem observation template with name value pair and use vocabulary to indicate if pregnant or not pregnant.
- Need to review both cardinality and conformance usage for each eICR data element (i.e. which are mandatory - null flavor not allowed)
- Need to review vocabulary for each Dataelement where applicable.
- Need to agree on a Title.
CSTE consensus derived Data Elements
Summary of DataElements mapped to CCDA templates.
Status: Draft
Status date: 20151018
ECR Datalement to MU2105 and CCDA Mappings
Use Case summary descriptions
- Use case diagrams created by Laura/Shu/Janet
Status: Draft
Status date: 20151018
eCR Context diagram and preconditions for use case with PH Intermediary system (e.g., PHCP)
eCR Context diagram and preconditions eCR without a PH intermediary system (eCR sent directly to PH)
- Use case diagrams created by AMS "Use Case diagram as part of producing the abbreviated DAM that I hoped would provide some input to this effort."
Status: Draft
Status date: 20151018
- Use case scenario from ASTHO
Status: Draft
Status date: 20151018
Draft DAM Diagrams
- DAM created by AMS
Status: Draft
Status date: 20151102
Word format: initial draft of the eICR Domain Analysis Model
Enterprise Architext format: initial draft of the eICR Domain Analysis Model
Pilots
- ASHTO Informatics Call for Participation in Electronic Case Reporting Pilot
Status: Unknown
Status date: 20151018
Project Scope Statement Electronic Case Reporting Using the PHCP
Issues/Hot Topics
List of issues
- Triggers code - currently not in scope for IG but need to be discussed. ( should they be separated IG ?)
- has been been mapped in template to DocumentationOf and draft valuest consisting of several code systems.
- Direct reporting to PHA vs intermediate step to PHCP/RCKMS decision suppor- what is scope of IG
- Using unconstrained (unchanged) CCDA section and entry templates for initial DSTU of message - will this create issue for PHAs if they require information not relevant to CR?
- FHIR version of CR resource alongside of SDC FHIR instead of V3 based CDA
Back to PHER activities