Skip to end of metadata
Go to start of metadata

Date: 2019-04-09

Facilitator:  Anthony Julian

Note Taker: Anne Wizauer  

Attendees


Name

Affiliation

xConstable Consulting Inc.
xMayo Clinic
xParker Digital Health Computing 
xHL7 CTO
xDuteau Design
xCANA Software and Service Ltd
xDeontik Pty Ltd
xJ2 Interactive
xBlue Wave Informatics


Guests


Name

Affiliation


AEGIS

Accenture

ICode Solutions

PKnapp Consulting

Create Decision from Template

Agenda Topics

Agenda Outline
Agenda Item
Meeting Minutes from Discussion
 Mover/SeconderVote
ManagementMinute ApprovalMinutes accepted via general consent

MethodologyWhat is Normative - issue raised by Jean

Jean reports this came up with some work he and Lorraine are doing with EHR. We have ways to ballot material at a Normative level, but what does that mean? To Jean it means you've gotten feedback from Implementers so you know the thing your balloting is valid and tested. The EHR functional profiles being normative...what does that mean? Ron: It goes back to how the EHR committee was conceived in the organization. They're creating a theoretical spec against which CMS is able to assert things about what constitutes an EHR. Should be able to do some kind of conformity assessment on whether they're using the profile and whether they're using it properly. Lorraine is concerned that they never do an STU.

Ron: They have no constituency at the implementation level, and there's no certification model. Lorraine: They're saying they shouldn't be doing trial use and they don't have an expectation of what is in there profiles is implemented. If we're doing that, what does it mean that we have these normative things? Jean: If we're going to ballot something at HL7, there has to be a purpose to that balloting. It shouldn't be just visibility. You should say why you're balloting it and what value it has. If it's normative, they should be able to say what it means that this thing is normative, and we need to be able to tell them what they need to do to be allowed to ballot normative. Hugh: if someone tells me something is normative, I would assume it's been through implementer validation and it's reasonably solid. What Ron is describing is a different kind of normative entirely, where there's no established implementer base. Perhaps it needs a different name to make it clear.

Wayne: Within HL7, the term Normative means something that's been approved by ANSI. ANSI doesn't say anything about testing. Ron: These aren't designed with interoperability in mind. I would call them definitional, a descriptor of something being used for policy purposes. Lorraine: They do have some mechanisms beyond that. One issue is that Normative means it's ANSI approved, but by our own processes we have a working assumption that the things we're promoting as Normative have had maturation via the draft process. We need a more precise definition of normative. 

Jean: Need to know the value of having something balloted at HL7 and what rules your product has around what it means to be normative. Lorraine: When we have new products come in, we need to define what a normative track is for that product. As we're going through the ballot guidance, there may be useful guidance on when you should go to normative ballot. Discussion over what ANSI certification means across the community. Could apply maturity model to normative standards. Hugh: You could go to normative but still remain at a lower maturity level. 

Next steps: Could make additions to ballot guidance, and request that SGB entertain a precept that methodology groups define what it means to be normative for new product types.




MethodologyCharacteristics of Realm Transferable Standards

Ron presents the updated version. Ron would like people to review and comment on the outline in the table of contents. Sent to Grahame, Lloyd and Ewout; Lloyd has responded with some suggestions. Reviewed Paul's comments. Several people on International Council are reviewing the most current version of the documents as well.  

ACTION: All to review/comment on the outline in the table of contents



Management Next agendaComments/feedback on Characteristics of Realm Transferable Standards table of contents

 Adjournment
 Adjourned at 4:57 pm Eastern

Supporting Documents

Outline Reference
Supporting Document
Minute Approval2019-04-02 ARB Agenda/Minutes
Characteristics of Realm Transferable StandardsRTSS PSS Decision&Documents


Open JIRA:

Key Summary T Created Updated Due Assignee Reporter P Status Resolution
Loading...
Refresh

Action items

  •