STD NBS Users Group Meeting November 14, 2017 3:00 4:00 PM ET - - PowerPoint PPT Presentation
STD NBS Users Group Meeting November 14, 2017 3:00 4:00 PM ET - - PowerPoint PPT Presentation
STD NBS Users Group Meeting November 14, 2017 3:00 4:00 PM ET Meeting Agenda Welcome and Introductions Charlie and Marvin Remarks from NCSD Charlie Remarks from CDC Surveillance and Data Management Branch Marvin
Meeting Agenda
- Welcome and Introductions – Charlie and Marvin
- Remarks from NCSD – Charlie
- Remarks from CDC Surveillance and Data Management
Branch – Marvin
- Presentation from Developers – Jennifer Ward (CSRA)
- Project Area Presentations
- Nevada - Elizabeth Kessler
- Alabama - Thomas Lee
Why Support Surveillance System User Groups ?
Foster STD Programs Learning From Each Other
User Group Audience & Purpose
- Audience: STD AAPPS funded grantees and other STD programs using
Maven software for STD surveillance and information management
- Purpose: Identify and share:
- Best practices
- Solutions to common problems
- Sources of technical assistance
- Identify opportunities to share resources and costs
- Dialogue with staff at CDC’s Division of Sexually Transmitted Disease
Prevention (DSTDP) Surveillance and Data Management Branch, National Coalition of STD Directors (NCSD) and Developers - CSRA
Participation is Essential for Success
NCSD Update
Charlie Rabins
About NCSD
NCSD is a national public health membership organization representing health department STD directors, their support staff, and community-based partners across 50 states, seven large cities, and eight US territories. Mission: To advance effective STD prevention programs and services in every community across the country. NCSD does this as the voice of our membership. We provide leadership, build capacity, convene partners, and advocate.
7
- New STD Website: www.ncsddc.org
- Recent launch of e-learning STD Program Evaluation
Training and Tools
- http://www.ncsddc.org/std-pett/
- http://www.ncsddc.org/std-pett-tools/
- Promote peer-to-peer TA/CB via the NCSD Weekly Email
Update
- Support Slack Communication Sites for STD Surveillance
System User Groups – PRISM, Maven and NBS
NCSD Update Item
Tools for User Group Communication
- Participate in User Group meetings, webinars and trainings
- Contact staff, peers and developers via email, phone and
Slack
- Use STD NBS Users Group Slack Site
- Post Resources
- Ask and Respond to Questions
- Share Experiences, Accomplishments and Challenges
- Suggest topics for Future User Group Meetings
- Connect on PC/MAC, smartphone, tablet – IOS, android
- Screen Share and Audio/Video Calls within Slack – up to 8
persons/sites
Poll Question
How often do you look at the NBS Slack site? (only one response)
- Daily or when there are new postings
- Weekly
- Occasionally
- I have joined but don’t use
- I have not joined
- APP Result Link:
https://www.confpal.com/surveyliveview.do?confid=1185&indicatorid=1354&objectsurveyid=675&type=bar
How to Join and Learn Slack
- 56 Current Members - 589 Postings and Messages
- If you haven’t joined the STD Maven Users Group SLACK Team Site,
- email us for another invitation
- Use link:
https://join.slack.com/t/mavenusersgroup/shared_invite/enQtMjcwMDQzMzc4MDY4LT hiYmNjMmY2MDRhNjViNDkxN2I3NDgzYjcyZDFiYzRlNjdhNjcwMmE2NmZhNmQ4MDQwN WRkYTI2NTBlMjAyYjU
- Email address – we will use your work or an email of your choice to invite you to join
- If work firewall blocks access to SLACK, access from personal ID and device (PC,
phone, tablet)
- System is Very Intuitive and Easy to Learn
- Help and training is available within Slack, on YouTube, on the internet
- Contact Charlie or Marvin for Questions or TA
CDC DSTDP Surveillance and Data Management Branch Update
Marvin Fleming
Presentation from NBS Developers
Jennifer Ward
CSRA
STD NBS User Group Meeting
November 14, 2017
Topics
- STD/HIV Surveillance and Case Management in NBS
- Available Training Resources
- Planned Upgrades
- Current Adoption Status
Support for STD/HIV Surveillance and Case Management in the NEDSS Base System (NBS)
What is the NBS?
- Patient-centric with a Master Patient Registry (MPR)
- Over 140 different diseases and conditions
- Reporting of notifiable diseases to the CDC using HL7
- Contact tracing, interview records, treatments, and vaccinations
- Customized data collection using ‘Page Builder’ functionality
- Customized reporting with data extract capability
- Security at the program and jurisdiction level
- Matching and deduplication services
- Receipt and automated processing of Electronic laboratory reports (ELRs)
- Data migration/exchange capabilities using Public Health Document Container (PHDC), including eICR
- User-defined decision support algorithms for automated processing of ELR and PHDC
Who is in the NBS Community?
The NBS is currently used by 22 of the 57 (39%) public health reporting jurisdictions.
19
- Nevada
- New Mexico
- Rhode Island
- South Carolina*
- Tennessee
- Texas
- USVI
- Vermont
- Virginia
- West Virginia
- Wyoming
NBS (22)
- Alabama
- Arkansas
- District of Columbia
- Guam
- Idaho
- Kentucky
- Louisiana
- Maine
- Maryland
- Montana
- Nebraska
USVI GUAM
Indiana is also joining the NBS community.
* SC currently only using NBS for TB
Support for STD/HIV Surveillance and Case Management in NBS
- Customizable STD and HIV Investigation Pages
- Printable Standard Forms
- Case Notification (Morbidity) to CDC
- Support for HIV Partner Services File (PSF)
- Case & Workflow Management
- Contact Tracing/Management
- Workflow Decision Support (WDS) in Support of STD
- STD/HIV Custom Reports
- Additional STD/HIV Data Analysis Tools
- STD Data Migration Utility
Customizable STD and HIV Investigation Pages
- Standard STD/HIV forms with ability to
customize, as needed, by the implementing jurisdiction.
- Includes:
- STD Investigation Form
- HIV Investigation Form
- STD/HIV Interview Form
- STD/HIV Contact Record Form
21
Printable Standard Forms
- Print blank or ‘filled’ standard CDC
forms for:
- Field Record Form
- Interview Record Form
- Provider Follow Up Form
22
Case Notification (Morbidity) to CDC
- Case Notification (Morbidity) to CDC
- NBS creates an STD NETSS file until CDC is able to receive HL7 messages for STD.
- When CDC is ready to receive HL7 case notifications for STD, the STD module in NBS is
already able to create and send HL7 messages per the CDC STD Message Mapping Guide.
- HIV case notification is not part of NBS (should still use eHARS).
- Partner Services File (PSF)
- NBS produces the PSF xml file for upload to CDC’s Evaluation Web.
23
STD NETSS STD HL7 PSF SAMS PHIN MS Evaluation Web
Case & Workflow Management
- STD Case Management
- Support for Co-Infection & Epi-Link (Lot Number) Concepts
- Ability to enter Referral Basis and Processing Decision when Creating an Investigation
- Data pre-populated into Investigations from trigger Lab Reports and Case Reports
- Place Entity available to track shared Hangouts/Places to Have Sex
- Ability to associate treatments across investigations
- STD/HIV Queues
- Messages Queue to alert staff to key changes in workflow to STD/HIV investigations of interest
- Supervisor Review Queue to provide supervisors with a clear view of items that require their review
24
Contact Tracing/Management
- STD-Specific Contact Record
- Configurable template provided to capture contact data import to STD surveillance process.
- View of Contact Record data in the Reporting Database.
25
Linkages are created between patient files/investigations.
Workflow Decision Support (WDS)
- Ability to manage incoming electronic laboratory and case
reports in an automated way, assisting staff in prioritizing and managing workflow to maximize available resources.
- Reduces burden on local investigators so they have more
time available for investigation activities, (e.g., high volume conditions like Gonorrhea and Chlamydia)
- Automatically creates investigations with default values (e.g. case
status, disposition, etc.) and notifies CDC.
- Actions Include:
- Mark the report as reviewed and remove the incoming report
from worker queues.
- Automatically create an investigation and set default values for
fields (e.g., set investigation status to ‘Open’ and case status to ‘Suspect’).
- Automatically create an investigation and generate a case
notification (report of morbidity) to CDC.
26
STD/HIV Customs Reports
- 31 custom reports available for STD/HIV program use:
- Case Analysis Reports (5 Reports),
- Program Activity Reports (15 Reports)
- Quality Assurance Reports (11 Reports)
- Report specifications included with training
documentation for NBS 5.1
- Provide information on the source and translations/
calculations for all of the data elements on each of the reports
27 https://nbscentral.sramanaged.com//redmine/documents/188
Additional STD/HIV Data Analysis Tools
- STD HIV Data Mart available with 200+ data elements for analysis.
- Contact Record and Interview record data views available, as well.
- Provides a very powerful analysis tool for any NBS jurisdiction adopting the STD/HIV
module.
- STD HIV Data Mart Design documentation that provides more information about this
data mart, including:
- STD and HIV code sets
- Data labels/locations in User Interface > Operational Data Store (ODS) > Reporting Database (RDB)
- Data transformations from ODS > RDB (e.g., calculations, concatenations, etc.)
28
STD Data Migration Utility
- NBS Implementation Guide for Data
Migration
- Detailed guide for migrating data from
legacy system
- NBS Data Migration Mapping Tool
- Tool used for mapping data from legacy
system (questions and answers)
- NBS Migration Process
- Scripts and Rhapsody routes used to create
xml documents to import the legacy data into the NBS
29
5.1
STD Data Migration Utility
A.
Legacy data is mapped into a pre-defined, simplified (flat file) data structure from the legacy system/data structure.
B.
NBS-provided Rhapsody Route is used to pull data from a flat file structure into CDA-compliant XML messages.
C.
XML messages are imported into the NBS as public health documents, which undergo basic NBS inspection and processing to de-duplicate, standardize, and route, which includes:
PHDC Import Process
Mapper Tool Rhapsody Routes PHDC Importer
- Event/Patient Matching
- Provider/Organization Matching
- Local to Standardized Terminology Mapping
- Security Assignment
- Workflow Routing/Decision Support Algorithm Application
- Email-Based Alerting
30
STD Data Migration Utility
- Ability to bring in labs, morbs,
treatments, and contacts associated with a case during a migration using the migration process.
- The same Patient to the right has a case
report, a lab report, and morbidity report imported into the NBS.
- The case report triggered an investigation
during the import process (i.e., a WDS algorithm was triggered), which also generated an NND notification to the CDC.
- The lab report and the morbidity report
that came in with the case report have been automatically associated with the auto- generated investigation.
10/14/2014 Gonorrhea Confirmed 2210941108 John Jaggerlish COMPLETED Open Fulton County CAS10011003GA01Documents (3) Morbidity Reports (1) Vaccinations (0) Treatments (1)
+ + + +
Patient Events History
Investigations (1) Lab Reports (1)
- Start Date
Condition Case Status Co-Infection ID Investigator Notification Status Jurisdiction Date Received
10/14/2014 11:58 AMProvider/Reporting Facility Test Results
Reporting Facility: MEDICAL LAB-JOHNSTOWN Ordering Provider: ROBINSON, BOB GC CULTURE POSITIVEDate Collected
10/14/2014Event ID
2210950136Associated With
CAS10011003GA01 Gonorrhea DOC10011003GA01 GonorrheaInvestigation ID Date Received
10/14/2014 11:58 AMProvider Treatment
STD CLINIC METRONIDAZOLE 2GTreatment Date
10/14/2014Event ID
2210578799Associated With
CAS10011003GA01 Gonorrhea DOC10011003GA01 GonorrheaDocument Type
Case ReportSending Facility Condition
Sending Facility: STATE DEPT OF HEALTH GonorrheaEvent Date
10/14/2014Event ID
DOC10011002GA01Associated With
CAS10011003GA01 GonorrheaDate Received
10/14/2014 11:58 AM 10/14/2014 11:58 AM Sending Facility: STATE DEPT OF HEALTH Gonorrhea 10/14/2014 DOC10011003GA01 CAS10011003GA01 Gonorrhea Lab ReportDate Received
10/14/2014 11:58 AMProvider Condition
STD CLINIC GonorrheaReport Date
10/14/2014Event ID
2210578711Associated With
CAS10011003GA01 Gonorrhea DOC10011003GA01 Gonorrhea 10/14/2014 11:58 AM Sending Facility: STATE DEPT OF HEALTH Gonorrhea 10/14/2014 DOC10011004GA01 CAS10011003GA01 Gonorrhea Morbidity Report31
Available Training Resources
Available Training
- Documentation of NBS STD Standard Reports
- STD Report Requirements Documents:
https://nbscentral.sramanaged.com/redmine/documents/188
- STD/HIV Module Training Recordings
- STD/HIV Module Training Recordings:
https://nbscentral.sramanaged.com/redmine/documents/215
- NBS sites already using the STD module have also shared training documentation
- Alabama STD Training Materials: https://nbscentral.sramanaged.com/redmine/documents/179
Available Training
- STD Training Videos on NBS Central
34
https://nbscentral.sramanaged.com/redmine/documents/215
- Session 1
- Creating an investigation for surveillance follow-up from
a lab report (electronic or manual)
- Closing surveillance follow-up and assigning for field
follow-up
- Session 2
- Creating an investigation for surveillance follow-up from
a Morbidity Report (aka communicable disease report (CDR), T2 Referral)
- Closing surveillance follow-up and assigning for field
follow-up
- Closing field follow-up and assigning for interview
- Updating interview status and documenting interview
records.
- Session 3
- Creating Contact records with and without interview
records
- Outgoing Out of Jurisdiction transfers
- Custom queries to pull OOJ line lists
- Session 4
- Incoming OOJs, contact investigations across
jurisdictions within a state
- Messages queue, supervisor review queue, notifications
(case notification (morbidity) to CDC) and related queues
- Use of place (hangouts)
- Associating additional lab reports, morbidity reports
(CDRs), etc. to an existing investigation
- Session 5
- Co-infection functionality
- Manage associations vs. associate investigations for
different events (lab, morbidity reports, contact records, interview, vaccination, and treatment)
- Session 6
- HIV Workflow for New Diagnosis, as well as referral for a
new STD for existing HIV positive patients
- Merging of lot #/s (Epi-Link ID)
STD Training Videos Available on NBS Central
Planned Upgrades
Planned NBS STD Module Updates
- Updates to STD module to accommodate case definitions for syphilis for 2018
(available in upcoming 5.2.0.1 patch release)
- Congenital Syphilis surveillance and case management scheduled to be in NBS 5.3
Release (available mid-January 2018)
- Updates to NBS STD Reports to address identified data discrepancies
36
Current Adoption Status
NBS Sites: STD Module Status as of October 2017
38
Jurisdiction Current STD System Notes IN PRODUCTION WITH NBS FOR STD (6)
Alabama NBS Live with STD (with DM) Idaho NBS Live with STD (with DM) Maine NBS Live with STD (without DM), data migration in process Montana NBS Live with STD (without DM) Nevada NBS Live with STD (without DM) Rhode Island NBS Live with STD (with DM) Virgin Islands NBS Live with STD (without DM) PLAN TO USE NBS FOR STD BUT NOT YET ADOPTED (7) Kentucky STD*MIS 4.1c Planned in production Jan 1 2018 Nebraska STD*MIS 5.2 Adoption date TBD; currently in discussion with NBS team New Mexico PRISM Adoption date TBD; currently in discussion with NBS team Vermont STD*MIS 4.1c Adoption date TBD West Virginia STD*MIS 4.1c Adoption date TBD Indiana PRISM Not yet in production with NBS. COULD USE NBS FOR STD (TBD) (3) Tennessee PRISM STD implementation potential for future (long-term) Wyoming PRISM STD adoption in Evaluation Guam (aggregate reporting) STD adoption in Evaluation
Jurisdiction Current STD System
NO PLAN TO USE NBS FOR STD (6) Arkansas PRISM DC MAVEN Louisiana PRISM Maryland PRISM Texas STD*MIS 4.2 Virginia MAVEN
If an NBS (or non-NBS) jurisdiction is interested in adopting the NBS STD module, please reach out to the CDC.
NBS Team Key Contacts
- Michael Wodajo
CDC Project Manager (NBS)
- O: 404-498-6675 | C: 678-733-4692
- E: gue@cdc.gov
- Marion Anandappa
CDC Technical Lead (NBS)
- O: 404-498-0575
- E: dza@cdc.gov
- Sumesh Sundareswaran
SRA Project Manager
- O: 470.419.6164 | C: 470-725-7333
- E: sumesh.sundareswaran@csra.com
39
- Christi Hildebrandt
NBS Product Manager
- O: 470.419.6147 | C: 404.386.3780
- E: christi.hildebrandt@csra.com
- Jay Nelson
NBS Production Support Manager
- O: 470.419.6156 | C: 678-358-6119
- E: Jay.Nelson@csra.com
- Jennifer Ward
NBS Product/Public Health SME
- O: 865.672.6295 | C: 678-431-5166
- E: jennifer.ward@csra.com
For more information please contact Centers for Disease Control and Prevention 1600 Clifton Road NE, Atlanta, GA 30333 Telephone: 1-800-CDC-INFO (232-4636)/TTY: 1-888-232-6348 Visit: www.cdc.gov | Contact CDC at: 1-800-CDC-INFO or www.cdc.gov/info
The findings and conclusions in this report are those of the authors and do not necessarily represent the official position of the Centers for Disease Control and Prevention.
Center for Surveillance, Epidemiology, and Laboratory Services Division of Health Informatics and Surveillance
Additional Topics for Discussion
- Legacy Data Migration – Considerations & Lessons Learned
- Data Quality Strategies
- Known Issues
- Demos Available
- Partner Services Information Data Entry
- Contact Tracing and Contact Data Analysis
- Use of Workflow Decision Support for Auto-Processing
Support for STD/HIV Surveillance and Case Management in NBS STD Data Migration Utility
- NBS PHDC Implementation Guide for
Data Migration
- Detailed guide for migrating data from
legacy system
- NBS Data Migration Mapping Tool
- Tool used for mapping data from legacy
system (questions and answers)
- NBS PHDC Migration Process
- Scripts and Rhapsody routes used to create
PHDC documents to import the legacy data into the NBS
42
5.1
Support for STD/HIV Surveillance and Case Management in NBS STD Data Migration Utility
A.
Legacy data is mapped into a pre-defined, simplified (flat file) data structure from the legacy system/data structure.
B.
NBS-provided Rhapsody Route is used to pull data from a flat file structure into CDA-compliant XML PHDC messages.
C.
XML messages are imported into the NBS as public health documents, which undergo basic NBS inspection and processing to de-duplicate, standardize, and route, which includes:
PHDC Import Process
Mapper Tool Rhapsody Routes PHDC Importer
- Event/Patient Matching
- Provider/Organization Matching
- Local to Standardized Terminology Mapping
- Security Assignment
- Workflow Routing/Decision Support Algorithm Application
- Email-Based Alerting
43
Support for STD/HIV Surveillance and Case Management in NBS STD Data Migration Utility using PHDC and WDS
- Ability to bring in labs, morbs,
treatments, and contacts associated with a case during a migration using NBS PHDC (public health document container)
- The same Patient to the right has a case
report, a lab report, and morbidity report imported into the NBS via PHDC
- The case report triggered an investigation
during the import process (i.e., a WDS algorithm was triggered), which also generated an NND notification to the CDC
- The lab report and the morbidity report
that came in with the case report have been automatically associated with the auto- generated investigation.
10/14/2014 Gonorrhea Confirmed 2210941108 John Jaggerlish COMPLETED Open Fulton County CAS10011003GA01Documents (3) Morbidity Reports (1) Vaccinations (0) Treatments (1)
+ + + +
Patient Events History
Investigations (1) Lab Reports (1)
- Start Date
Condition Case Status Co-Infection ID Investigator Notification Status Jurisdiction Date Received
10/14/2014 11:58 AMProvider/Reporting Facility Test Results
Reporting Facility: MEDICAL LAB-JOHNSTOWN Ordering Provider: ROBINSON, BOB GC CULTURE POSITIVEDate Collected
10/14/2014Event ID
2210950136Associated With
CAS10011003GA01 Gonorrhea DOC10011003GA01 GonorrheaInvestigation ID Date Received
10/14/2014 11:58 AMProvider Treatment
STD CLINIC METRONIDAZOLE 2GTreatment Date
10/14/2014Event ID
2210578799Associated With
CAS10011003GA01 Gonorrhea DOC10011003GA01 GonorrheaDocument Type
Case ReportSending Facility Condition
Sending Facility: STATE DEPT OF HEALTH GonorrheaEvent Date
10/14/2014Event ID
DOC10011002GA01Associated With
CAS10011003GA01 GonorrheaDate Received
10/14/2014 11:58 AM 10/14/2014 11:58 AM Sending Facility: STATE DEPT OF HEALTH Gonorrhea 10/14/2014 DOC10011003GA01 CAS10011003GA01 Gonorrhea Lab ReportDate Received
10/14/2014 11:58 AMProvider Condition
STD CLINIC GonorrheaReport Date
10/14/2014Event ID
2210578711Associated With
CAS10011003GA01 Gonorrhea DOC10011003GA01 Gonorrhea 10/14/2014 11:58 AM Sending Facility: STATE DEPT OF HEALTH Gonorrhea 10/14/2014 DOC10011004GA01 CAS10011003GA01 Gonorrhea Morbidity Report44
Legacy Data Migration – Considerations & Lessons Learned
- The most important (and time consuming piece of the process) is ensuring the data quality of the
legacy data (i.e., reviewing and cleaning the legacy data. Each migration has been unique from a data/data quality perspective.
- Perform SERIOUS validation of migrated data in staging BEFORE going into production rather than after
going into production.
- Involve the state STD folks early on in the process, so they have sufficient time to perform data validation.
- For any local codes that were added to STD*MIS (especially lab test codes), you will need to ensure the
code do not contain any spaces.
- Notes that are longer than 1950 characters will be truncated to 1950 characters, as NBS only supports Notes
up to 2000 characters.
- States have used production data in their staging environment to perform ‘test runs’. They have
used the production dataset to make sure the migration brought in the data as expected.
SITES ARE HIGHLY ADVISED TO PERFORM ALL TEST RUNS USING PRODUCTION DATA SNAPSHOTS OR PRODUCTION-LIKE DATA.
Legacy Data Migration – FAQs
- How long did the process take once the source tables were created?
- This highly depends on the volume of data, as well as the configuration/set up of your
environment
- With smaller record counts, the time to process is reduced.
- What is the difference between the processes for editable and non-editable data?
Do they both have to pass the NBS audits or is the data imported without the NBS checks?
- The editable data is read from the CDA XMLs and is written in the NBS operational tables as it
would be for a native NBS event.
- For the non-editable data, the patient is created in NBS and the CDA XML document related to
the event is linked to the patient. The data is directly read from the XML and is displayed in a ‘view’.
- Both sets of data go through the same data checks, since they have to confirm to the CDA.
Legacy Data Migration – FAQs
What is the most important thing we should keep in mind while doing the migration?
- The quality of the legacy data; legacy data can have varying levels of quality.
- We have detailed many data validations in the migration guide, but while going through the data,
if you think a field doesn’t contain the right format/type of data then it should definitely be checked.
- Other key considerations include:
- Staff Availability (Technical and SMEs)
- Volume of Data
- Timeline for Implementation & Cutover Plan
Data Quality Strategies
- Use of Business Rules Engine to ensure data quality for both NND reporting, but
also for analysis and reporting
- Sites should ensure Case Status, Confirmation Date, and Diagnosis are all populated (required if)
a Disposition has been entered for a case.
- These three data elements are key for the ‘canned’ STD reports provided in the NBS; if these data
are not collected, counts may appear suspect in reports.
Known Issues
- STD Reports
- Currently being reviewed to better understand cause(s) of data discrepancies
- Congenital Syphilis
- To be added in NBS 5.3
Please stop by the NBS Booth if you have interest in any of the following:
- General Overview of STD Module in NBS
- Data Analysis for STD Module
- Customizing STD/HIV Pages Using NBS Page Builder
- Additional Detailed Demos Available
- Partner Services Information Data Entry
- Contact Tracing and Contact Data Analysis
- Use of Workflow Decision Support for Auto-Processing
Project Area Presentation
Elizabeth Kessler
Nevada
Helping People. It’s who we are and what we do.
User Migration from STD*MIS to NBS
Chose one local health authority to test NBS STD Modules
1
Formed a super user group to expand testing
2
Created training materials that were released to
- ther local health
authorities one month prior to launch of NBS Production
3
Users were trained over a
- ne-month
period on data entry in NBS
4
Soft start was
- initiated. This
allowed for auditing of cases to minimize
5
After going live in production, continual guidance and training
- pportunities are
sent out and managed by the STD Program
6
52
Helping People. It’s who we are and what we do.
Benefits of NBS
53
- Improved data collection
- Easy to use customizable
page builder modules
- Allows for supervisor review
- f cases prior to closure and
notification
- Better interface with ELRs
- User friendly
- More resources and
support
Helping People. It’s who we are and what we do.
NBS Challenges
NBS does not have module available for Congenital Syphilis User queues required additional training for supervisors to be fully comfortable Transferring cases and labs out of jurisdictions required development of additional business processes NBS Reports for STD are still in need of development Full historical data migration
54
Helping People. It’s who we are and what we do.
Looking Forward
Nevada is working toward migrating from several STD*MIS 4.2 instances, into one instance of STD*MIS 5.2 Full historical data migration is planned for the future Nevada continually looks forward to the release of new features and opportunities within NBS
55
Helping People. It’s who we are and what we do.
For more information Visit the Division of Public and Behavioral Health website at: http://dpbh.nv.gov/ Contact Elizabeth Kessler STD and Hepatitis Program Manager Nevada Division of Public and Behavioral Health ekessler@health.nv.gov 775-684-5997
56
Thanks for Participating
- We hope you found this meeting worthwhile
- If you have comments about or suggestions
for improving the Maven Users Group, please email us
- Charlie Rabins crabins@ncsddc.org
- Marvin Fleming mqf6@cdc.gov with
comments or suggestions for improving the user group
Project Area Presentation
Thomas Lee
Alabama
ALNBS STD/HIV Data Migration
From Back to
GC-RNA GC-DNA CT-RNA CT-DNA N.
. gonorrh
- rrhoe
- eae by TM
y TMA: Positive - (Final) Ref Refer eren ence Ran Range: e: (Negative) - (Final)
C.
- C. trachoma
- mati
tis by TM y TMA: Positive - (Final) Ref Refer eren ence Ran Range: e: (Negative) - (Final)
ALNBS STD/HIV DATA MIGRATION
Make sure you have recommended system specifications on
database server
- Physical memory: 16 GB
- Disk Space 300 GB
Database configuration
- Recovery model set to simple
- Log file option set to autogrowth/maxsize value of by 10%
NBS Release 5.0 Ensure you have MS Access 10 for mapping tool: recommended to
be on same server as database
STD/HIV configured (Including published pages for STD/HIV) Upgrade STD*MIS data to 5.2 if needed
Alabama NEDSS Base System(ALNBS) STD (09/06/2016)
NBS Functions
STD Last Release Current Release Notifiable Disease Investigation Core Demographics Messaging Technical Support Reporting VPD PAM Meningitis (BMIRD) PAM Hepatitis PAM Animal Rabies PAM Foodborne PAM STD TB Lead Security
Where does the data come from?
State Health Department ICP & Lab Tech (Hospital)
Security
Integrated State / Local Data Repository
Private Labs & Hospital Labs (ELR HL7) County Health Department
Run in staging environment first, note times for scheduling
production run
Plan! Plan ! Plan !
- Timeline for data migration
Reviewing and cleaning legacy data prior to migration Set up STD users and providers in NBS Data Transform Run Rhapsody routes and import cases/contacts/labs/morbs Run batch processes Verification
- Reviewing NBS STD module for any state customization
- Training staff
- Go-live
THE OLD THE NEW