1. Spencer Crosswy Paul Schluter The Center for Medical Interoperability
RTM Governance Model
Spencer Crosswy
Paul Schluter
The Center for Medical Interoperability

2. RTM used for many purposes
IEEE
11073
10101
IHE PCD
TF2
PHD
OTHERS?
RTM
hRTM
NIST RTMMS
terms
terms, co-constraints,
cont. hierarchies
“Support the management of IEEE nomenclature” [IEEE P /D3r7] “Define and constrain the semantic content of IHE PCD messages. [ “Capturing new terms to support the IEEE ‘Personal Health Devices’ (PHD) initiative “ [IHE PCD TF-1]

3. Status Quo – adding content to RTM
Proposal
IHE PCD
PCHA/Continua
IDC Group
Guidelines
RTM
hRTM
NIST RTMMS
Ways to improve:
Broader participation in curation process
Improved scalability
Structured curation process
Codified guidelines
Versioning

4. Goal: Governance model for Rosetta Terminology Mapping
Principles:
Resilience – governance is stable to changes in participation and resources
Efficiency – model allows timely assessment of proposed RTM content
Quality Control – ensures proposed RTM content is of high quality
Structure – content lifecycle is fully defined
Stability – allows predictable evolution of RTM with versioning and release cycle
Neutrality – content consideration should be objective and unbiased
Simplicity – model is clean, straightforward, not overengineered

5. Status Quo Content Proposal RTM Content Proposal hRTM Content Proposal
Guidelines
IHE PCD
Content
Proposal
RTM
hRTM
NIST RTMMS
PCHA/Continua
Content
Proposal
IDC Group
Content
Proposal

6. End Goal Policy Content Proposal RTM Content Proposal hRTM Content
IHE PCD
drives
Content
Proposal
Governing
Body
NIST RTMMS
PCHA/Continua
RTM
Content
Proposal
hRTM
IDC Group
Content
Proposal

7. Governing Body Purpose: Aspects to consider: Enforcing quality control
Reviewing content proposals (new content and recommended deprecations)
Curation of existing RTM content
Retaining documentation with justification for all RTM modifications
Aspects to consider:
Organizational structure (e.g. chair/co-chair, voting body, etc.)
Membership (open to all? intentional representation from various interests?)
Decision-making process (how are decisions made? voting?)
Efficiency (balancing quality and expediency)
[1] IEEE P /D3r7

8. Governance Policy Purpose: Aspects to consider:
Defining content “quality” and guidelines for proposal submission
Defining content lifecycle process
Defining RTM versioning & releases
Aspects to consider:
What are minimum requirements for proposed content? e.g.
Standard format? Form to fill out?
Proposals should be well-formed and well-documented.
What is “quality”? What should be assessed when reviewing content proposals? e.g.
Is a new term clinically or technically necessary?
Is it described with sufficient clarity, unambiguous, and useable by clinicians?
What impact does a proposed deprecation have?
[1] IEEE P /D3r7

9. From Malcolm Clarke. Talking point – not an endorsement.
Content Lifecycle
Should build on lifecycle proposals in RTMMS and 1010R “Term Approval and Management”
Should remain agnostic to standards that reference RTM, and focus solely on RTMMS as a central terminology management system
Must accommodate proposed additions and proposed deprecations
Potential phases:
PROPOSED
PROVISIONAL
PUBLISHED/ZOMBIE
DEPRECATED
PROHIBITED
Is PUBLISHED/ZOMBIE a phase? Or an attribute?
From Malcolm Clarke. Talking point – not an endorsement.

10. One potential vehicle: Create RTM IEEE standard - includes content and governance model
Policy
defines
IHE PCD
drives
Content
Proposal
Governing
Body
RTM
hRTM
NIST RTMMS
RTM
IEEE
11073
Standard
PCHA/Continua
Content
Proposal
IEEE
Balloting Process
IDC Group
Content
Proposal
establishes

11. One potential vehicle: Create RTM IEEE standard - includes content and governance model
Policy
defines
IHE PCD
drives
Content
Proposal
Governing
Body
RTM
hRTM
NIST RTMMS
RTM
IEEE
11073
Standard
PCHA/Continua
Content
Proposal
IEEE
Balloting Process
IDC Group
Content
Proposal
establishes
Content
Stages
Creation
Final Vetting
Submission
Governance
Codification
Release

12. IEEE RTM Standard Release Cycle
Major version – coincides with release
Minor version – periodic snapshots with latest provisional terms

13. BACKUPS

14. 10101R Annex G This language does not belong in 10101:
“Provisional terms shall not be released in production devices.”
“Use of [deprecated] terms shall be indicated as an error.”
This language is OK, provided it is merely informative
“After selection for inclusion to RTMMS, a proposed term shall be allocated a provisional Reference ID and term code that may be used for development and interoperability testing.”
“After a period as a provisional term, a term shall be given final approval for inclusion to RTMMS “
“Terms designated maintenance shall become deprecated.”
This language does belong in 10101:
“Approved terms [in RTMMS] shall be included in the next revision of IEEE for ballot to become designated as a published term.”