December 3, 2009
Attending: Kevin Souza, small group chair; Michael Barbouche, Simon Grant, Chandler Mayfield, Jesse Friedman
The group recommended the following technical approaches for the educational trajectory:
- For places where values will be predictable on a national level, provide a recommended list of values. For example, when describing medical specialty, recommend using specialties recognized by the Accreditation Council on Graduate Medical Education and the American Board of Medical Specialties. Those outside of the United States would be able to use a list of specialties recognized in their nation.
- Provide a date time stamp for when data was submitted and by whom. The standard should allow for the ability to indicate the source of the data for a single activity/entry and for the educational trajectory as a whole. For pilot purposes, schools may have one source or author of the data - the person putting together the spreadsheet.
- Provide categories accompanied by a free text description to allow for flexibility and the ability to mature the standard over time.
- Leverage LEAP2A for describing activities and develop custom categories for use within that infrastructure.
- Valerie and Simon will expand on Pat's data and produce an example to see what the LEAP2A specification with educational trajectory categories would look like. Jesse with input the same data into UCSF Mahara system to see the differences between the current export and the example developed by Simon and Valerie.
- We will use LEAP2A ability to uniquely reference a competency.
- Valerie will seek feedback on these decisions from the MedBiquitous Technical Steering Committee, which meets via teleconference December 9.
February 3, 2010
Attending: Kevin Souza, Jesse Friedman, Simon Grant, Chandler Mayfield
The group had the task of making recommendations for operationalizing the technical specifications in a medical school envoinment with varying degrees of technical sophistication, ranging from home grown systems to pen and paper. The group offered the following:
- UCSF will offer insights as to where data may be found, what would be involved in putting together an xml feed, and what conversations others would need to have to pull the data together.
- For the short term (ie the pilot), sending data using CSV (comma separated values) format is adequate.
- For the long term vision of implementation, creating a browser-based application that allows schools to input data would serve as a good bridge for those with fewer technical resources.
- The group recommended inviting system vendors to participate in specification development.