February 5, 2016 Financial Management Work Group Conference Call
Return to Financial Management Home Page
Conference Call Schedule
- Occurs on Fridays, 4 PM Eastern
- Phone Number: +1 770-657-9270 Participant Passcode: 686300# (alternative for US if the first number doesn't work: +1 888-321-4501)
Attendees
| Member Name | |
|---|---|
| Kathleen Connor Co-chair | x |
| Beat Heggli Co-chair | |
| Paul Knapp Co-chair | |
| John Moehrke Security Co-Chair | x |
| Lorraine Constable | |
| Andy Stechishin | x |
| Mark Scrimshire | |
| Grahame Grieve | |
| Corey Spears |
Agenda
Discuss FM CPs addressing FHIR CD requirements.
- FM CP 9533Change Contract signature datatype from string to FHIR Signature datatype, and change cardinality to 1..*.
- FM CP 9534Change Contract.actor to Contract.agent
- FM CP 9536 Change the name of current Contract.subject to Contract.topic, and update current definitions
Follow up on implementation of 7752 #1073 - Replace value set with FHIR Signer Type value set
- SSD-SD interim cochair election
Minutes
- RE: FM CP 9533Change Contract signature datatype from string to FHIR Signature datatype, and change cardinality to 1..*.
CP text: Change Contract signature datatype from string to FHIR Signature datatype and change cardinality to 1..*. Provide documentation in the element description and front matter explaining that the Signature.who type may be a signer on behalf of a signing party. This addresses the use case where an App or mobile device signs a contract/consent directive on behalf of the organization accountable for complying with the contract/consent directive. Make Signature 1..* for use cases in which there may be more than one signature. Examples: Company policy requires that a signer of a contract having a value over $1 million must have two signatures, the grantor/grantee party to the contract, and a second signature from the company's CFO. Signer is a minor with divorces parents who have joint custody. Policy requires that all legal guardians of a minor who signs a consent directive must co-sign that consent directive.
- John Moehrke's Friendly Amendment FM CP 9533Change Contract signature datatype from string to FHIR Signature datatype, and change cardinality to 1..*] to change cardinality of Contract.signer.type and Contract.signer.role to 0..1 to support use cases where there is no signer but there may be a business reason for having a signature, was tabled until next call because beyond scope of discussion and the implications of doing so in terms of a legal contract haven't been throught through. We also need a couple of use cases to illustrate the need. There may be alternative solutions even though Contract.signer is optional. Kathleen to include in 2-12 agenda.
- REFM CP 9534Change Contract.actor to Contract.agent
CP text: Correct erroneous change of Contract.actor and Contract.term.actor to "party" as this conflicts with use of Contract.signer.party. Intended change was from Contract.actor and Contract.term.actor to Contract.agent and Contract.term.agent to align with FHIR AuditEvent and FHIR Provenance use of W3C PROV terms. A possible issue, which Lorraine Constable pointed out during the FM discussion, is that "agent" is a term also used to refer to environmental or chemical entities that also "cause" an event, although the event might be characterized as a Reaction vs. the Action caused or potential caused by a human agent. There may need to be discussions with FHIR community about how to enable both usages without collision.
- FM CP 9536 Change the name of current Contract.subject to Contract.topic, and update current definitions
CP text: Change the name of current Contract.subject to Contract.topic, and update current definitions as follows:
Contract.topic Definition: Who and/or what this Contract is about: The matter of consideration about which an agreement is made, which includes an offer or promise of future actions that is accepted. The party making the offer is the grantor, and the one accepting the offer is the grantee, and the matter under consideration is what is being conveyed or "granted". Examples include obligations, rights, and valued items such as goods and services.
This change supports a requirement for in the FHIR Contract ConsentDirective profile for a ConsentDirective.topic which is constrained to "Patient Information governed by this Consent Directive." in a FHIR ConsentDirective.
Contract.subject Definition: The entity impacted by the contract or of interest to the parties to the contract.
- Follow up on implementation of 7752 #1073 - Replace value set with FHIR Signer Type value set
Existing Wording: "The Digital Signature Purposes, an indication of the reason an entity signs a document. This is included in the signed information and can be used when determining accountability for various actions concerning the document. Examples include: author, transcriptionist/recorder, and witness.
Copyright Statement: These codes are excerpted from ASTM Standard, E1762-95(2013) - Standard Guide for Electronic Authenticaiton of Health Care Information, Copyright by ASTM International, 100 Barr Harbor Drive, West Conshohocken, PA 19428. Copies of this standard are available through the ASTM Web Site at www.astm.org."
This value set defines its own terms in the system http://hl7.org/fhir/contractsignertypecodes.
Comment: Kathleen negatively balloted this value set in January and it was supposed to be replaced with a signer type value set that incorporated the relevant ASTM signature types as signer types. The ASTM codes denote the context in which a particular signature was executed. That is orthogonal to the purpose of Signer Type element - which is to specify the role that the entity played when executing a signature on a contract or any of its profiles. I have provided that value set to CBCC FHIR Facilitators, but time ran out before it could be loaded into the build. Kathleen submitted this value set structured for inclusion in v.3 vocabulary for March Harmonization. Hopefully either the v3 or the FHIR value set will be uploaded for FHIR Sept ballot. Replace the ASTM Signature Value Set with FHIR Signer Type value [1] for v.3, renamed SignerType to Legal RoleType to enable broader use since there is no comprehensive "actor" value set of structural and functional roles in v.3. FM Legal RoleType Initial Harmonization proposal
- All CPs approved one by one with John moving and a second from Andy. 0-0-2
- RE SSD-SD interim cochair election - Decided to have email vote to ensure wider participation. Andy moved to elect Gora Datta mHealth cochair, as SSD-SD cochair replacing Pat van Dyke. Lorraine seconded. Motion carries 0-0-4 with votes from Andy, Lorraine, Kathleen, and Paul.
