MEDSS user group meeting October 2012

1. MEDSS user group meeting October 2012

2. Agenda • Follow-up questions from last time (15 min) • Maven configurability (15 min) • ELR and De-duplication, overview (30 min) • Discussion around ELR issues (15 min)

3. Questions/thoughts from last meeting?

4. Maven Release structure

5. Maven Platform EDSS & OMS Forms Workflow Letters Reports Birth Defects Forms Workflow Letters Reports Trauma Registry Forms Workflow Letters Reports Justice CaseManagement Forms Workflow Letters Reports Case Management M A V E N CORE Business Rule Engine Linked Records and People Workflow and Task Triggers Security Rules (Roles, Groups, Program Area, Jurisdiction, Audit Trails) De-duplication (Persons& Records) Geocoding and Map Integration Ad Hoc Reporting and Data De-normalization Real-time interfaces (XML, Web Services, …)

6. Maven Development Timeline 1/2 Case Management M A V E N CORE PRODUCT 2005 Business Rule Engine Workflow and Task Triggers 2006 Deduplication 2007 Security Rules (Program Area, Jurisdiction) and Case Sharing 2008 Geocoding and Map Integration Maven Portal Outbreak and Cluster Management Roster Imports Internationalization Support Stateful Workflow Expressions Adhoc Reporting

7. Maven Development Timeline 2/2 Survey Management M A V E N CORE PRODUCT 2008 Two Factor Authentication 2009 Reference Parties 2010 Roster Updates Web Services 2011 Data De-normalization Full Text Search Party Attributes Scheduling and Appointment Management Batch Tasks and Scheduling PDF Print Template Support

8. How do we determine what changes to make?

9. Process for what changes to include in core • Feedback from customers • Feature Request JIRA tickets • Feedback from Maven user group • Contract obligations • Customer Support calls (usually monthly) • Change requests • Prioritization • Implementation

10. What is a change request? • Change to either core or the customer layer after completed implementation of a deliverable. Usually has a price and implementation lead time. Estimates include specification, development and QA. • Change requests involving changes to core • Implementation has to be done so the change doesn’t impact everyone, usually comes with a setting to turn on or off. • Usually take longer time to implement since impact on all customers has to be taken into consideration • Change request only affecting customer layer • Examples of these type of CRs are: additional custom reports, additional data conversions and rosters, additional case processor rules, print tokens etc. • Delivery time depend on available resources at Consilience Software and time for development.

11. Maven customization

12. Maven Platform EDSS & OMS Forms Workflow Letters Reports Birth Defects Forms Workflow Letters Reports Trauma Registry Forms Workflow Letters Reports Justice CaseManagement Forms Workflow Letters Reports Case Management M A V E N CORE Business Rule Engine Linked Records and People Workflow and Task Triggers Security Rules (Roles, Groups, Program Area, Jurisdiction, Audit Trails) De-duplication (Persons& Records) Geocoding and Map Integration Ad Hoc Reporting and Data De-normalization Real-time interfaces (XML, Web Services, …)

13. Who can change what? • Consilience Software • Core changes • Custom reports (reports requiring complicated logic or design) • Custom workflows (workflows needing coding) • Case processor rules • Add print tokens • Make changes to importers such as the ELR and ADR importers • Somewhat configure lab tab and person tab. • Data migrations • Custom roster importers • Drop down list in core (party links, case link, gender, event status)

14. Who can change what? • MN-IT. MEDSS team or server staff (can also be done by Consilience using a change request) • Changes to the models, reference codes and concerns • Adding and changing workflows (SQL or expression based) • Add print templates using existing tokens. • Create ad-hoc reports • Upload and extracting cases/event using MIF format • Add and define security roles and groups • Change system settings (turn on/off de-duplication for example) • Configure de-normalized tables • Designated super users • Add ad-hoc reports

15. What is Maven Model Manager? • Program used by the MEDSS administrators to make modifications to the models.

16. What can we do in Model manager? • Add questions and define field type such as free text, selection or dates. • A selection choice field could be a drop-down, checkboxes, radio buttons, search and select etc. • Define simple validations such as ‘has to be entered’ or ‘has to be larger than’, or specific string formats, etc. • Define when a field should be visible (based on disease or previous answers) • Define parent and child relationships between questions such as Medication (parent) and Dosage and Route (children) • Allows us to make questions repeatable (“Add New” link) • Define Concerns such as a notification that a Hospital Admission Date comes after the Hospital Discharge Date • Allows us a way to create wizards (Virtual Question Packages) so that question ordering can more closely mimic existing forms

17. Limitations to model manager • Model manager don’t have the ability to pre-populate questions dynamically based on answers in previous questions. • Questions can’t be set to be populated with results from a rule • Questions can’t be set to have complicated math, the only way to do that would be with a rule. • It’s tricky to set Questions to have complex validations such as “allow letters but not decimal points” • Model manager can’t modify the reference code lists (can be done in the admin interface).

18. ELR and de-duplication

19. ELR

20. Process once the data hits MEDSS

21. New ELR workflows • New ELR workflows are used to tell users that a new lab result has been received • The workflows are triggered by the field ‘ ELR reviewed’ is set to NO (done automatically for new lab reports) • To minimize the number of events any given user has to review, the workflows has been setup to show only certain diseases – for example ‘new ELR – foodborne’ should have only foodborne disease, ‘New ELR – STDs’ should only have STD diseases. This requires that the correct disease has been assigned in a previous step • Some program areas have New ELR workflows showing only New ELRs for a certain MDH project# (this requires project numbers being received)

22. Raised issues related to ELR and De-dup • Manual de-dup of person records is very time consuming, it seems like the system should be able to do a better job of finding duplicates. Why can’t the system identify a match for ELRs with the same specimen# as a match? • Events doesn’t get merged and lab information doesn’t get added to the correct event, when I de-dup the event I don’t find a possible match. • If a person has been manually de-duped (which is a tedious process), the events also has to be reviewed and de-duped as a second step. • When doing person de-dup, the list of possible matched seems to include too many possible matches (irrelevant or not even close matches are showing up)

23. Raised issues related to ELR and De-dup , cont • Some New ELR workflows still has too much stuff in them, making it hard to review. - this can be adjusted by making the criteria for the workflows smaller • The system seem to be doing a bad job of identifying what disease the lab information belongs to. • It’s very time consuming to review the New ELR workflows and it seems like we get a lot of stuff we don’t care about

24. Lab tab vs QPs • ELR information is received into the Lab tab • Multiple tests/results are organized for an event based on specimen#, date and test. • For example John Doe can have one event of TB with multiple lab tests and results. • QPs are setup to have the ‘best or case defining’ test/result information, to be used for CDC extracts etc • Previous decision was made that there was a manual decision step to decide what test/result to use • System could define the ‘correct’ test/result if logic can be defined • Proposed Change Request to have a way on the lab tab to manually ‘check’ the ‘case defining’ test/result which would then populate the questions for CDC transmission. (Need more discussion)

25. Questions