WR220070713telcon

Wrappers R2 project telcon

Friday 15th June 11am ET
Phone Number: 702-894-2444
Participant Passcode: 984125 
https://www.gotomeeting.com/join/369287397
gotomeeting Meeting ID: 369-287-397
Project page - MCCI/CACT R2 Project

Agenda

Admin

• Approve notes of previous meeting ? WR220070608telcon
• Agree scribe
• Introductions and roll call

actions from minutes

• Actions carried forwards
  • (CM) Identify an INM co-chair for the project
  • (CM) Initiate discussion on usage for converstaionId
  • (CM) Initiate discussion on context conduction (agreed that this would be done having looked at the implementation of the change, and Lloyd agreed to contribute on fleshing out the requirements

Balloting Admin

• confirm content delivery timelines

• Project page - MCCI/CACT R2 Project

notes from the call

Attendees: Dale Nelson, Charlie McCay, Lloyd Mckenzie

Dale reported that he did not have the source for the current MCCI, but would be working on some sort of MCCI content over the weekend

We noted that there has not been progress on query and master files, but that maybe we just to MCAI this round, and roll the changes into those documents following the reconciliation of comments on MCAI.

There was discussion of the problem that Don Lloyd reported - saying that publishing could not publish two versions of the same material side-by-side. This is a problem that needs to be addressed as the MCCI/MCAI R1 material is still being referenced by all of the current ballot material, and will be used for the comming normative release. We agreed that if publishing could not render two releases of the wrappers specifications, then the wrappers R2 drafts should be published as PDF files.

We agreed that a new classCode should be proposed for Conversation, and that the definition of the class code Infm should be generalised so that it can be used for the interaction class.

We agreed that the controlActProcess is the subject of the interaction, and the payload act is the subject of the controlActProcess.

The authorOrPerformer and Overseer remain participations of the controlActChoice rather than the interaction, because the controlAct is the act of gathering the information together, and the interaction is a defined (part) realisation of that controlAct, not something that is independantly authored. A controlAct (such as suspendMedication) may result in a number of interactions (

For detected issue we agreed that an Inform Request relationship could be added to detected issue to convey whether the issue should be notified to the user and/or the system administrator and/or the application technical support. There was some discussion as to whether there was a need for multiple descriptions of the same error, but a concrete usecase for this was not produced.

A severity relationship has been added to detectedIssue by Canada, and that should be considered for inclusion.