LavaCon Las Vegas 2016 Presentation

1. TRACKING CRITICAL CHANGES
ARE YOU REGULATORY COMPLIANT?
PROVE IT!
PRESENTED BY TRISTAN MITCHELL

5. Identification
Representation
Management
of XML Change

6. OBVIOUS TRUTH #1
Content Changes

7. “Everything
changes and
nothing
remains still”
“Change is the
only constant”

8. “To improve is to
change, so to be
perfect is to
have changed
often.”

9. OBVIOUS TRUTH #2
Stakeholders want
to see the changes

10. Authors
Editors
SMEs
Reviewers
CustomersAuditors

11. OBVIOUS TRUTH #3
Change must first be
identified before
you can show it

12. Revision log
Version
control
Change tracking
Comparison
Native Markup
(e.g. DITA)
Processing
instructions
Identification
@rev attribute
@status
attribute
Release management
domain
Representation

13. LESS OBVIOUS TRUTH #1
Structured content
presents opportunities
around change

15. LESS OBVIOUS TRUTH #2
Identified change can
be published

16. Demo

18. MAKING IT WORK
Provide stakeholders
with changes relevant
to their needs

19. Authors
Editors
SMEs
Reviewers
CustomersAuditors
Tracked changes
Tracked changes
Published changes
Change summary
Published changes
Change summary
Tracked changes
Published changes
Change summary
Published changes

20. MAKING IT WORK
Molina HealthCare
Case Study

21. MOLINA HEALTHCARE
• Word-based solution using change tracking
• Redline PDF ‘printed’ from Word
• Content moved to DITA-based system
• Conditional processing supports alternate requirements
• Change-tracking is no longer possible due to reuse
• Comparison used to create DITA source for redline publishing

22. MOLINA HEALTHCARE
XMetaL
SDL
HTML
&
CSS
PDF
DITA
OT
Antenna
House
Steven.Moldenhauer@molinahealthcare.com
DITA workflow

23. SUMMARY
@TristanDeltaXML
• Content changes, constantly
• Think about who your change stakeholders are
• Build a mechanism for identifying and representing change
• Remember why you chose XML
• Provide changes in a way that meets stakeholder needs
tristan.mitchell@deltaxml.com