MEDSS user group meeting
October 2012
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)
Questions/thoughts from last meeting?
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).
ELR and de-duplication
ELR
Process once the data hits MEDSS
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)
Raised issues related to ELR and De-dup
1. 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?
2. 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.
3. 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.
4. 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)
Raised issues related to ELR and De-dup , cont
1. 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
2. The system seem to be doing a bad job of identifying
what disease the lab information belongs to.
3. 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
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