MEDSS user group meeting
September 2012
Agenda
• Recap of the MEDSS project (5 min)
• Maven improvements and upcoming features (15 min)
• Maven configurability (15 min)
• How to get data out of Maven, focus on De-normalized
tables. (60 min)
• ELR issues (15 min)
MEDSS Project/deliverables
• Delivered modules
– ELR, replacing LARS
– TB, including conversion of TB data and HL7 message for TB
– Birth Defects
– EHDI
– Foodborne, including conversion of FB data
– Vectorborne and zoonotics
– ABCs
– Pertussis, including conversion of pertussis data
– Other vaccine preventable diseases
– STDs, including conversion of STD-MIS and STD Infonet
– ADR
• Remaining
– Hepatitis, including conversion of Hepatitis data
– Conversion of VPD Track
– HL7 Generic and arboviral messages
– Bluecard replacement/provider portal
Maven 4.1 Enhancements (4.1.1 - 4.1.6)
Maven 4.1 Enhancements
• Significant amount of new functionality added between 4.1.1 and
4.1.6 in the past 12 months
– Motivation to get new improvements and functionality out faster
– Drop in backwards compatible builds for Maven 4.1
– Maven 4.2 for major new functionality (DB schema changes, new modules)
• Main areas for Maven 4.1 incremental improvements
– Deduplication
– Print templates
– User interface
• Important to check out release notes!
Maven 4.1 Enhancements
• Question Packages
–
–
–
Enforced questions
· An enforced question had to be entered before saving (vs required which only
indicates that an answer is missing)
Pre-populate new iterations
· Default new values to previous iteration values
Improved layouts (labels vs. fields spacing) (4.1.6)
• General User Interface
–
–
–
Improved Address entry
Advanced searching
Improved dynamic questionnaire management for outbreaks
• Workflow Management
–
–
Improved rendering for custom workflow columns
Display current case workflow status (4.1.6)
Question Package Layouts - Before
Question Package Layouts - After
Improved search (4.1)
Advanced Search (4.1.6)
Case Workflow Status (4.1.6)
Maven 4.1 Enhancements Cont.
• Print Templates
–
PDF print template support with visual editor
• Administration
–
–
–
–
Additional notifications and alerts on administration interface
· Misconfigured processing modules, workflows
· System and JVM configuration settings
· System performance alerts
· Database schema/index verification alerts
· New Maven versions
Improved data archiving configuration in the administration interface
· XML import/export processing modules
Watermark/Banner for sites
Fast application switching
Environment Marking 1/2
Environment Marking 2/2
Maven Deduplication Enhancements
• Heuristic name matching
–
–
Jaro-Winkler Edit Distance
Special rules for Asian names (2-3 letter names, *NG suffix)
• Heuristic DOB matching
–
Mistyped date/months/year plus 2-digit transpositions within the field
• Heuristic address matching
–
–
–
Incomplete addresses
Numerical street names
Misspelled street names
• Improved history matching
• Relaxed exception rules based on scoring
–
Gender mismatch vs. score >= 100
• New special rule for common names
–
Name + DOB match
• Option to auto-merge case records after person merge
• More detailed audit trails on user/batch decisions
Heuristic Address Matching
Maven Release structure
Maven Platform
EDSS & OMS
Birth Defects
Forms
Workflow
Letters
Reports
Forms
Workflow
Letters
Reports
Trauma
Registry
Justice Case
Management
Forms
Workflow
Letters
Reports
Forms
Workflow
Letters
Reports
Case Management
M
A
V
E
N
Business Rule Engine
Linked Records and People
Workflow and Task Triggers
Security Rules (Roles, Groups, Program Area, Jurisdiction, Audit Trails)
C
O
R
E
De-duplication (Persons & Records)
Geocoding and Map Integration
Ad Hoc Reporting and Data De-normalization
Real-time interfaces (XML, Web Services, …)
Maven Development Timeline 1/2
Case Management
2005
2006
M
A
V
E
N
Business Rule Engine
Workflow and Task Triggers
Deduplication
2007
2008
C
O
R
E
Security Rules (Program Area, Jurisdiction) and Case Sharing
P
R
O
D
U
C
T
Outbreak and Cluster Management
Geocoding and Map Integration
Maven Portal
Roster Imports
Internationalization Support
Stateful Workflow Expressions
Adhoc Reporting
Maven Development Timeline 2/2
2008
2009
M
A
V
E
N
2010
2011
Survey Management
Two Factor Authentication
Reference Parties
Roster Updates
C
O
R
E
Web Services
Data De-normalization
Full Text Search
P
R
O
D
U
C
T
Party Attributes
Scheduling and Appointment Management
Batch Tasks and Scheduling
PDF Print Template Support
How do we determine what changes to
make?
Process for what changes to include in core
1. Feedback from customers
1.
2.
3.
4.
5.
Feature Request JIRA tickets
Feedback from Maven user group
Contract obligations
Customer Support calls (usually monthly)
Change requests
2. Prioritization
3. Implementation
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.
Maven customization
Maven Platform
EDSS & OMS
Birth Defects
Forms
Workflow
Letters
Reports
Forms
Workflow
Letters
Reports
Trauma
Registry
Justice Case
Management
Forms
Workflow
Letters
Reports
Forms
Workflow
Letters
Reports
Case Management
M
A
V
E
N
Business Rule Engine
Linked Records and People
Workflow and Task Triggers
Security Rules (Roles, Groups, Program Area, Jurisdiction, Audit Trails)
C
O
R
E
De-duplication (Persons & Records)
Geocoding and Map Integration
Ad Hoc Reporting and Data De-normalization
Real-time interfaces (XML, Web Services, …)
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)
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
What is Maven Model Manager?
• Program used by the MEDSS administrators to make
modifications to the models.
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
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).
How to get data out
Options
• Custom reports and exports, built by Consilience Software
–
–
–
Can basically do whatever you want
CSV extract is a custom report.
NETSS extracts is an example of a custom extract
• Ad-hoc reports, built by MEDSS admins or designated staff
–
–
–
Simple reports or SQL
Output to screen or extracted to excel format
Have limitations
· Will provide the value of a field, not the code
· Repeatable fields causes problems.
• De-normalized tables
–
–
–
–
Built by MEDSS admins
Can be set to use values or codes for fields
Manages repeatable fields.
Access is outside of MEDSS
• Case extracts from admin interface (in MIF)
• Jasper reports
–
Available in 4.1.6
de-normalized tables
Jasper Reports References
• Web site
–
–
Jasper Reports
· http://jasperforge.org/projects/jasperreports
Jaspersoft iReport Designer
· http://jasperforge.org/projects/ireport
• Resources/Books
–
–
–
–
–
–
JasperForge Community
· http://jasperforge.org
iReport 3.7 by Shamsuddin Ahammad
JasperReports Library Ultimate Guide
· https://www.jaspersoft.com/store/jasperreports-ultimate-guide-documentation
iReport Designer Ultimate Guide
· https://www.jaspersoft.com/store/ireport-ultimate-guide-documentation
The Definitive Guide to JasperReports (Expert's Voice) by Teodor Danciu and Lucian Chirita
The Definitive Guide to iReport (Expert's Voice) by Giulio Toffoli
ELR and de-duplication
ELR Process
De-duplication
Step 1:
Person De-dup, if there is a match the person records
are merged or they get listed for manual de-dup.
Step 2:
Event De-dup, if the event is within the timeframe for a
match and the disease is the same they get merged. If
it’s within a set grace period it will get flagged for manual
review.
Step1 always has to happen first.
Limitations with ELR and De-dup
• Person will not match unless there is enough data. (birth
date, name, address, gender is used). Threshold can be
adjusted but have to prevent from incorrect merges.
– Lab results often doesn’t have enough for a match
• If the person didn’t match (or wasn’t merged) the events
will not be identified as matches.
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)
Questions