August, 2018 CBCP Conference Call

Attendees

	Member Name		x	Member Name		x	Member Name		x	Member Name
x	Johnathan ColemanCBCP Co-Chair		x	Suzanne Gonzales-Webb CBCP Co-Chair		x	Jim Kretz CBCP Co-Chair		x	David Pyke CBCP Co-Chair
x	Kathleen Connor Security Co-Chair		x	Mike Davis		.	John Moehrke Security Co-Chair		x	Diana Proud-Madruga
x	Chris Shawn		.	Neelima Chennamaraja		.	Joe Lamy		.	Greg Linden
x	Irina Connelly		.	Saurav Chowdhury		x	Dave Silver		x	Francisco Jauregui
.	Mark Meadows		.	Amber Patel		x	Becky Angeles		.	Jennifer Brush
.	Mohammad Jafari		.	Ali Khan		x	Ken Salyards		.	Michael Gu
x	David Staggs		.	Bonnie Young		.	Ioana Singureanu		x	Beth Pumo
.	Lawless		.	Ken Lord		.	[mailto:]		x	[mailto:]

Back to CBCP Main Page

Agenda

1. Roll Call, Agenda Review
2. Meeting Minutes approval: (not ready)
   • July 31
   • July 26 - confirm
   • June 17
3. eLTSS Update - Irina / Becky
   • eLTSS gForge folder: https://gforge.hl7.org/gf/project/cbcc/docman/eLTSS%20-%20%20ONC%20Electronic%20Long-Term%20Services%20and%20Supports
4. Privacy - Is Privacy Obsolete update - Mike Davis
5. FHIR Consent
   • FHIR CPs for review
   • FHIR Consent CPs are located: link to ALL Consent Change requests
   • FHIR Consent / Consent contract
     • Continued discussion
     • Vote?
6. Baltimore WGM DRAFT posted (Suzanne working on)

Meeting Minutes DRAFT

Chair - Dave Pyke

No meeting minutes

eLTSS

• Final (corrected) PSS posted in gForge: <<Add Link>>

• final touches are being added to white paper
• ONC will be reviewing - please send any additional comments to Irinia LAST DAY
• PSS IS APPROVED! by TSC
  • once received information from CMS and ONC - Irina will submit items to publishing before the 19th with final version
• regarding formatting: adding line numbers ARE helpful (and preferred for commenters)

Privacy Obsolete

• no new information, no update

for remainder of converstion - Suzanne

• comments are fhire resources cannot be linked are trued (mike)
  • ou ca't get to a contract by going through a consent resource - cannot be linked in that way
  • you attach a link via a sourc for a consent.sourc (DPye)
• paul its not htat you ca't point from one resource to another; resources must be linked together (that is not restful

dp - cannot go from contract to consent

Paul:proposal as written - that you ever have a contract... and further and you can only look up the contrack via resource; in he event you have a resource, ou must crate a registry... and

• architected like that is not restful

dp - a registry of what...? paul - dp has entired se; document would be linked as paul

kathleen - ineffeictnet and not restful ; if they have chose to use the FHIR contract for that purpose.

Johnathan - you have heard some opposition to the language as writte - have not heard modification to more language that is agreeable;

DP - we need to vote down the language; and then start the wordsmithing.

dp the current objection is that we are constraining the language.

paul - we are not telling them how we can building... we are limiting how...

johnahtna - not comfortable as written

ONC interoperability standard advisory 2019 includes bppc appc fhir consent and fhir contract as candidates for computable consent (kathleen)

• johntath - suggest where consent resournce is one of the best ways / or preferred ways (change from only way); we cannot specify information.

dp - only place aware of that are us are using contract is in US and mihin, both of which are Us- realm... kc - mihin , cener (DSTU 2) we have not done fhire consent either, dp and no one says you ave to change a dstu2 implmentaiton

MOTION ; accept the language of the motion as stated (david/paul) Abstentions: becky objections: mike , pyke affirm paul: obj, 703franciso; obj Johnathan: obj

stags: obj diana: obj kathleen: object jim: obj beth: ? no response irinia: ? no response

motion: fails

Johnathan: paul Lithuania example

current motion:
* consent resource is the correct (and best) way to store and exchange computable consent agreemtns in a FHIR environment
* formal consent docuents are contracts an dyou may use the contract resource to capture that aspect of them for attachement to the consent resource as a source document
* while consent information may sometimes be found in documentReference, Binnary, Contract and other resources, Consent is the principle resource for reprenseint consent-related information and is the endpoint where systems should expect to find thisinformaiton 

new: mike: IG are the est way to present that type of information paul cannot force busieness process to be technologically...

• not sure why we are dong this at all.. not opposed t guidance; i.e. its like saying java is the preferred software to write language...

jim: would you endorse first bull if remove: 'to store' dp : updated 'to exchange'

kathleen - would like to put out that the entire statement should be removed; and... in contract... leave contract as is. some feel claim starts as an invoice... wold like go ack, do not recraft and take the governance issue in trying to set another... we are not repsenting the discussion is between FM CPCP for one onewg depends on what we do... (40:52) paul - find to thingk that the ocnsen resource is a well esigne resource to implement (from someone) for a registry/exchange of a resigtray.. that's behind th front oor. but its cant be used for a reposity because it doesn't have the full contenet

let's strike this.. leve situation as normal as it has been.. thenwe dot' meed tom make a statne, we dot' nee to statee a preernc, an dnot move forward... ey gus do what you want to do. kath; ther aree two artifaicts infhir recognized by ONC and cananda certain source cantalk about cases; vecaue goernancne issue down the road are more far reaher, we can come up with word here but is

thorugh practition resource;

kathl - the name of th eresouce is consent, the cosnetract is aconsetn directive and that is what seems to being munged in this conversation; th

• use case is computable cosennt

Johnathan - informative white paper - comparative capabilities; so implementers can make an informative decision moving forward; people are jumping from one to other - without considering the other

• mike agree 0 would satisfy the intent of the three bullets

striking language, and move forward in another direction. mike: who is going to write? - katlen - if johnahtna will be project lead, kathleen will write part for one section; someonelse will need to write another section johnathn - wants it to be usedfl and … guidance where we can post kath - if wgs agree it can be placed in the fhir ballot as part of guidance

moving this to a white paper to be balloted in FHIR (potentially) PSS and other administrivia will be started once start of paper has been initialized

dave will forward language to presenter of language results of the vote and additional details

motin to adjorn: (Suzanne) meeting ended 9:50 Arizoan time--Suzannegw (talk) 12:51, 7 August 2018 (EDT)