The Standards Game

Did you ever wonder how standards organizations work?  I created this little game to give you an idea.  It's a game best played with 4-8 players.

It doesn't start out with rules, though, instead it starts off with bylaws (because bylaws can be changed).  The bylaws and operations manual are purposefully confusing, ambiguous and subject to interpretation by the players (because that is the way that governance works).

Bylaws:

1. The object of the game is to gain the most influence.
2. To gain influence, you must successfully complete or kill projects.
3. Anything agreed to according by consensus of the players is legal.  Consensus in this case means without objection.
4. Momentum is important.  Any action taken on a turn that is completed by a player with consensus of the group (without objection by any other player) stands, unless it is immediately reversed.  The player immediately following must use two influence cards to raise a motion to reconsider actions in the previous move, and all other players must use one influence card to vote to reconsider.  A successful vote to reconsider is considered sufficient to reverse the action (because in the real world, after a successful vote to reconsider, the next move is to vote to change the action, and if you wouldn't consider changing it, you wouldn't vote to reconsider).
5. There can be at most 4 projects before the board at a time.
6. No more than 50% of players may be aligned identically, and all alignments must be present in game play (see starting play).  Any time a player is to be assigned an alignment that violates this rule, they must be assigned a different alignment (at random unless there is only one choice).  

Operations Manual

Objective

He or she with the most influence at the end of play wins. 

Influence

Influence is measured by the number of cards a player has in his or her hand at the end of play.  Influence cards are distributed based on influence, and are used to perform actions in the game.  Influence cards come from a standard deck of 52 cards (with or without jokers).

Paying with influence: In many cases, members can select which influence card they use from their hand.  However, when paying with influence, the card thus chosen MUST be chosen randomly from the member by another member.  This represents the often random costs on the use of influence in the real world.

Starting the Play 

Each player is initially given four influence cards, the first is dealt face up and determines the player alignment.  This card must remain face up in front of the player. Alignment determines the powers that a player may execute during play.

If the face up card is in the suit of Clubs, the player is a member of the public sector.  The public sector can hire consultants (they provide cards to consultants who act on their behalf during the consultants turn, as well as act in their own turn).  The public sector can create only one project per game, but can commission consultants to do so as often as they like.

If the face up card is in the suit of Diamonds, the player is a consultant.  Consultants can be hired by the public sector an unlimited number of times.  A consultant can create only one new project during the game that has not been commissioned by a customer.  

If the face up card is in the suit of Hearts or Spades, the player is a consumer or producer in private industry.  A member of the private sector can initiate projects as often as they like, but commission a consultant to act for them only once per game.

The game is played in a series of quarters.  Each of these is played in round format.  

Determining the agenda.  In each quarter, players play in the order of their face up card, from highest to lowest.  At the beginning of each quarter a play can replace their face up card with another face up card of the same suit from their hand to change the order of their turn in the agenda.

A token is used to indicate who currently "has the floor".  The player with the floor may act.  When they are done, they must pass the token to the next player on the agenda.  When that player accepts the token, the current player's turn is over, and all actions they performed are completed.

New Business.  When a member has the floor, they may propose a new project.  To propose a new project, the member announces the proposal by selecting an influence card from their hand, and placing it face up before themselves on the board.  They must then place an influence card face up on the project to show that they are participating in it.  They can then solicit participation from other members.  Each member choosing to participate must place one of their influence cards face up on the project card.  No more than half + 1 of the members may participate in any single project.

Determining the Project Leader. The highest rank participant card above a 9 becomes the project leader.  In case of ties, the first played card of the same rank is the leader.  If less than three members choose to participate in the project, the project fails, all cards are discarded, and the proposer must pay an influence card.

A proposed project that has at least two participants (including a leader) moves forward to the voting stage.  Those that do not remain active but not ready for voting, see old business below.

Old Business: A proposer of a project that does not yet have a leader must solicit leadership, withdraw the project, exchange their participation card with a higher card, or pay an influence card to keep the project alive.  If another participant wishes to pay an influence card to keep the project alive, they may do so during the proposer's turn.  The withdrawer of a project must pay an influence card to withdraw the project.

A proposer or leader of a project that has a leader may also withdraw the project, citing inability to reach concensus.  The withdrawer of a project must pay an influence card to withdraw the project.  Anyone participant opposed to withdrawl can pay an influence card to keep the project alive.  All cards played on a withdrawn project go to the discard pile.

Opening the Ballot: Any project with a leader can declare itself ready to be voted on by declaration of the project proposer or leader, and by the use of an influence card by any one of the project members.  When ready for voting, turn the project card face down (but leave others face up).

Distribution of Influence Cards:   Before voting, influence cards are distributed as follows:  Members get one card for each project they are a participant in.  Proposers of a project get one card for each project they have proposed (remember that a proposer must be a participant initially). 

Voting:  Voting is a random activity.  Members shuffle their hand and remove two cards.  They must then place a randomly selected card down on each project they are participating in, representing their vote.  A red card is a negative vote, a black card is a positive vote.  To determine the outcome of the vote, tally all red and black cards separately, (counting Aces as 1, and face cards as 11).  If the black pips exceed the red by more than double, the ballot passes without need for reconciliation.  If the red pips exceed the black pips by more than double, the ballot failed, and must be re-balloted or withdrawn.  Discard all votes on a failed ballot.  Otherwise the ballot must go through reconciliation (see below).

Reconciling Comments.  During this phase (which immediately follows voting), an attempt is made to clarify the results for ballots which have not yet failed or passed.  Each player is given the floor once again to perform resolution actions.  Members can use their influence to change votes of another member by playing a card of a different color on that member's original vote.  Once the tally of red vs. black votes for a project exceeds the 2:1 ratio, that project has been reconciled.  If it started out in the black, and was passed through reconciliation, then it is concluded, and influence is awarded for it.

If it started out in the red, and was passed through reconciliation, then it is ready for reballoting in the next cycle (but someone must use influence to get it to the next voting stage).

If it goes into the red, regardless of where it started, the proposer and leader must pay influence cards, and the project has failed.

Redeeming Influence on a successful project: Return to your hand each card used to represent your participation, or for voting, and each card used by other members to influence your vote (make it more positive or negative) on a project. Return also to your hand the project card if you are the proposer.  If you are the leader or the proposer of a project, take an extra influence card from the deck.

Budget Crisis

If at any time all influence cards are no longer available (because they have all been distributed), declare a budget crisis.  Each member must contribute one influence card, plus one for each project they have proposed or lead to the organization.  The quarter is immediately closed, and a new quarter starts.  No voting or reconciliation takes place in the closed quarter due to the crisis.

Lapse in Membership

Due to the need to pay an influence card, a member may have to use their "alignment card" to complete an action.  The first time this happens to a member, such a result introduces a temporary laps in membership, and the alignment card is turned face down.  The player can take no actions during any subsequent round, until they have paid their dues.  They do benefit from the first available distribution of influence, and simply return one of those influence cards back to the influence stack.  At this time they then turn that card face up and can resume in play.  The second time this occurs, they must pay two influence cards, and so on.  If they cannot pay sufficient influence within two quarters to return to active membership status, they are out of the game.  A lapse in membership can also simply be declared by the member, in which case they are treated as a lapsed member, and they must pay the influence penalty to return to active play.  

All the cards of a member exiting the game are returned to the discard pile.

Lack of Balance

At any time in which the balance of participation of any one alignment in the game exceeds 50% of the remainder, the game is over.  This can happen through lapse in membership.

Members

Players can enter and leave the game at will.  New players become new members at the start of a quarter, when they are given their initial 4 cards.  

OK, play-testing anyone?

IHE and CCDA Entry Comparison

I just finished my first pass review of the comparison between IHE and Consolidated CDA Entries.  Here are my findings (and recommendations):

• ACT/text is required by IHE to contain a reference to the narrative which is being described by the entry.  HL7 Consolidated CDA recommends but does not require this (Keep the IHE requirement).
• The CCD Episode Observation Template is optional in various places in CCD 1.0, and so included (but not referenced) in IHE, but is not mentioned at all in Consolidated CDA (Leave it unreferenced).
• The severity template is not explicitly referenced in various places where it could be used in IHE (reference it as optional).
• Medications, Immunizations and Supply need detailed review, do medications first.
• There are several places where classCode, moodCode or other structural attributes already fixed by CDA are referenced by the templates in Consolidated.  This is not done in IHE.  (Fix the values because IHE ALSO uses these templates in messages).
• HealthStatusObservation is referenced by CCD 1.0 (and thus by IHE indirectly), but not mentioned in Consolidated in the same places (It was garbage, kill it).
• ValueSet and CodeSystem constraints are strangely missing from my output.  I must have a bug somewhere. I'll need to reprocess the data to address those issues.  Code constraints are present though, so it shouldn't be too challenging to figure out.
• Procedure is also going to need detailed review.

It appears that 4 out of 20 templates are going to need a pretty detailed review, and that 12 of them should be pretty easy, and 4 might need more investigation, but should also be fairly easy.

So, another chunk ready for review.

   Keith

P.S. And today, I applied for admission to the Clinical Informatics Master's program at OHSU.

Real Progress on IHE and CCDA Harmonization

I've gotten to the point where I've been able to compare IHE and Consolidated CDA sections based on MDHT content.  For the most part, my findings are that most sections will not be a huge problem to decide what to do with.

There are some general rules that apply to all sections:

• section/code has a fixed value coming from LOINC
• section/title is present
• section/text is present

The latter most rule may be challenging for some sections like physical examination where subsections are present, but given that it says nothing about the fact that section/text could just contain white space, I could live with it in these cases.

For all the sections in the IHE Final Text, IHE and C-CDA agree on LOINC codes.  We don't necessarily have the SAME set of constraints listed, but that can be normalized.  This is something that just about everyone gets right.

We also agree mostly one what kinds of things belong in each section, e.g., medications in a medication section, et cetera.

The place where IHE and HL7 seem to disagree most is on the structure of a Physical Examination Section.  IHE allows it to be multi-level with subsections.  HL7 allows multiple levels, but doesn't reference the subsections any more as it did in the H&P Note, and requires section/text in the Physical Examination Section.  That's worthy of some discussion when we review this section in the future.

I have a two IHE sections that appear to be missing in the MDHT content:
Assessments Section: 1.3.6.1.4.1.19376.1.5.3.1.1.13.2.4

Procedures Section: 1.3.6.1.4.1.19376.1.5.3.1.3.12

I'll have to model those and rerun.  I'm looking forward to Friday when I can actually present and discuss something to the IHE folks who have been patiently waiting for me to present something.

Here are the major decision points we need to address (with my recommendations):

1. The rules for every section (listed above).
2. The choice of the entries optional section or entries required section (take the best match).
3. Cardinality of Family History Entries; do we match HL7 or require entries (depends on the IHE template).
4. Handling Results: IHE has requirements on content, HL7 has requirements on organizers which require content (shift to HL7 way).

My next step is to look into the entries.  I don't think we need to worry about documents.  In fact, as best I can tell, documents are national extension content.

Patient Access Summit II

Thursday of last week, I spent a half day in the Indian Treaty Room of the Eisenhower Executive Office Building.  I was joined by at least 50 others, including patients, health IT vendors, healthcare providers, and quite a number of federal agency staffers, as we talked about the next steps for providing patients with access to their data.

Kicked off by Matthew Holt (@boltyboy) of Health 2.0 fame, and hosted by Todd Park and Farzad Mostashari, this meeting was a followup from last year's Patient Access Summit (which I also attended with my daughter).

We reviewed the progress we've made since our first meeting (about a year ago), and identified the things that we still need to work on.  As an outcome of this meeting, we identified six separate gaps to address:

1. Awareness:  More needs to be done to raise awareness among patients, providers and health IT vendors about patient rights and technology available to access data, and Blue Button Plus alignment with Meaningful Use incentive programs.
2. Services:  Identifying needed services (e.g., data reconciliation and filtering), and prioritizing them was another issue.  We expect that industry will develop services as the needs are identified.  In other words, the ONC role here is more to shine a light one what is needed.
3. Trust. "Trust me", and "I'm here to help" are two statements that get even scarier when you start them off with "I'm with the government".  There's a lot that needs to be done to develop trust.  Some of that is time, and some of that is awareness.
4. Provisioning.  This is more about provisioning patients, and/or making it easy to provision patients with a Direct address, or an identity supporting OAuth 2.0.  It was focused on workflow and user experience rather than technology.
5. Pull.  We need data holder participation, and when we asked for it, a number of them (in fact, about 1/4 of the room) raised their hands.
6. Payers. There's an interim payer specification that we'd like to see payer's start using, and a need to get that on a standards track.

In reviewing the list of gaps, one thing that Farzad noted was that we didn't have any issues around standards needing to be developed, which was a big different from where we started a year ago.

I did manage to leave Farzad speachless when I asked if we should hold our calendars open for Patient Access Summit III next June.  Next year, I think we need to be in the West Wing.

IHE and HL7 Jointly Balloting Healthy Weight Profile

On Monday, IHE announced the opening of its Public Comment period for several profile proposals.  Today, HL7 announced an out of cycle ballot occurring concurrently with the IHE public comment period ON THE SAME CONTENT.  This is part of the pilot process announced by the two organizations earlier this year.

The purpose of this out of cycle ballot is, as explained in the announcement, is to help IHE and HL7 understand the mechanisms necessary to jointly ballot material, and at the same time, to obtain more input for IHE on profiles using HL7 standards.

Getting this ballot together was a bit of a challenge, but we (IHE and HL7) did manage to make it happen, and we already have a list of things that we can do to simplify this in the future.

   Keith

Slacking Off?

Not really.  I've just been finding it hard to write blog posts and code and specifications and go to training and ... all at the same time.  Since Sunday I think I've had an average of 4 hours of sleep a night.

What's going on?

Let's see, IHE just released some profiles that you should comment on.  HL7 and IHE are working on their joint balloting initiative, expect some news soon.  I've been providing some feedback for the HL7 Board about implementer's use of HL7 Standards and Open Source.  The ABBI PULL workgroup has been moving along without me for the past few weeks, but they are still making progress.  I'll get an update on that project tomorrow after I meet up with a few folks in DC to follow up on this meeting.  It's nice not to be the only person writing code on that project, but now I've got a ton of catching up to do to get my code back in shape and shift it to another repository.  HQMF is moving along.  We've been addressing some of the trickier editing bits over the past couple of weeks.  I owe them some text which I hope to get out this week.  I've been dealing with a bunch of questions about Consolidated CDA and QRDA lately as I run into some trickier implementation bits.  One of our engineers found a bug that makes some QRDA templates not possible to be used with some CCDA templates, but that will be addressed in a future release of CCDA, and there is interim guidance on that coming from HL7.  We found another issue in a bit of a model in MDHT, but that bug has been reported (it's an XOR constraint on author/assignedAuthor and author/representedOrganization that should be OR instead).

I just booked my summer vacation to London in the 10 days between delivery of a major milestone in one project, and IHE  Meetings and the HL7 Board retreat (the same week unfortunately, so I'll be missing half the IHE meeting).

That means I need to get my code working for the CDA Harmonization project done by the end of the month and start generating the profile content.  I've gotten to the point that I know I can get the differences between the sections, its just, as a former colleague used to say, a simple matter of writing the code.

I have another major deliverable due for an internal project, also by the end of the month, and a third due for another international project.

I have to finish up my application for attending the Master's degree program.  The two remaining bits are my letter and my transcripts (I took the GRE's last week).  The letter should be done this week, and I should have the transcripts on their way by then as well.

IHE PCC is going to be looking for a new planning cochair this year as I step back for a couple of years to focus on my degree (and address the fact that I've been a cochair for eight years, 4 in technical and 4 in planning).  If you are interested in the position, let me know.

I'm trying to get my house ready to go on the market, because my mother wants to move in with us.  We are thrilled, but there are a slew of small projects that need to be done.  Fortunately, I had a good year, and can do them.

I just accepted a small writing gig to update a chapter in a book that's a few years out of date, and have to figure our where that fits in.  Oh, and send them the paperwork.

I spend last Sunday in DC for the third annual DC gathering of The Walking Gallery.  It was way too short, and while I could have spent the rest of the week in DC, I had training scheduled for Tuesday through Thursday.  I'm bailing on tomorrow mornings training because after I scheduled the training I was asked to attend another meeting, and it was one of those invitations that you don't turn down.

All in all, life is busy, but also good.  I'm certainly looking forward to vacation in England.  We'll be staying at a friend's place a bit more than a hour from London.  I can't wait to get home from this trip.  And I need a nap, but that's what planes are good for.

Anyone heard of any progress on cloning technology?

IHE Profiles for Public Comment

This finally arrived in my inbox. I encourage you to comment, especially on the Internet User Authentication profile (profiling OAuth 2.0), and on the CDA Harmonization (which discussion methodology by which the profile will be created, and how IHE will version templates).

Keith

---

IHE IT Infrastructure Technical Framework Supplements Published for Public Comment The IHE IT Infrastructure Technical Committee has published the following supplements to the IHE IT Infrastructure Technical Framework for public comment in the period from June 3 through July 3, 2013: Document Sharing Metadata Volume 3, Section 4 Redocumentation Document Metadata Subscription (DSUB) Internet User Authorization (IUA)  The documents are available for download at http://www.ihe.net/Technical_Framework/public_comment.cfm. Comments submitted by July 3, 2013 will be considered by the IHE IT Infrastructure Technical Committee in developing the trial implementation version of the supplements. Comments can be submitted at http://www.ihe.net/iti/iticomments.cfm. IHE Patient Care Coordination Technical Framework Supplements Published for Public Comment The IHE Patient Care Coordination Technical Committee has published the following supplements to the IHE Patient Care Coordination Technical Framework for public comment in the period from June 3 through July 3, 2013. CDA Harmonization (CDAH) Early Hearing Detection and Intervention-Workflow Definition (EHDI-WD) Patient Care Plan (PtCP) Referral/Order Linking (ROL) The documents are available for download at http://www.ihe.net/Technical_Framework/public_comment.cfm. Comments submitted by July 3, 2013 will be considered by the Patient Care Coordination Technical Committee in developing the trial implementation version of the supplements. Comments can be submitted at http://www.ihe.net/pcc/pcccomments.cfm. IHE Quality, Research and Public Health Technical Framework Supplements Published for Public Comment The IHE Quality, Research and Public Health Technical Committee has published the following supplements to the IHE Quality, Research and Public Health Technical Framework for public comment in the period from June 3 through July 3, 2013. Data Element Exchange (DEX) Healthy Weight (HW) Research Matching (RM) Vital Records Death Reporting (VRDR)  The document are available for download at http://www.ihe.net/Technical_Framework/public_comment.cfm. Comments submitted by July 3, 2013 will be considered by the Quality, Research and Public Health Technical Committee in developing the trial implementation version of the supplements. Comments can be submitted at  http://www.ihe.net/qrph/qrphcomments.cfm.