- Current: The AAMC needs some kind of organizational approach in the CI to tell which pieces of the curriculum come earlier or later. Removing the Academic Levels and not replacing them with anything would remove AAMC’s ability to know the order the curriculum occurs in.
- CIWG Decision: No change
- Rationale: Level to Phase change is superficial with no changes to underlying data dictionary or logical model. Marketplace level change of data model not warranted.
Sequence Block (#19) and Integration Block (#18); Page numbers 36.
- Current: two organizational concepts for events – sequence blocks with start/end dates and durations, and integration blocks without start/end dates and durations.
- Goal: to make a system that is flexible enough to accommodate different curriculum and curriculum evolution, but also one that is user-friendly in its word choices and as simple as possible in its documentation requirements.
- Create the concept “course/module” to replace sequence blocks
- To hold/organize events in the CI
- Synonymous with block/unit (for our CI purposes, understanding that there’s a valid counter argument here)
- Still have the same qualities as sequence blocks do now (e.g., titles, description, duration, learning objectives, can be nested etc.), with the caveat that we will allow courses to cross over phases (formerly academic levels), as was voted on but never implemented in MedBiq release 1.1
- Include field for course/module “type” as the CI already does this with clerkship type (rotation or integrated are the current choices), allowing users to choose more than one. Categories to include:
- Discipline-based (e.g., pharmacology, medicine)
- Systems-based (e.g., The Gastro-Intestinal System, Food to Fuel)
- Integrated (i.e., normal/abnormal presentations)
- Clerkship (predominantly clinical, real-patient experiences)
- Rotational (i.e., course repeats throughout year but contains different cohorts)
- Longitudinal (i.e., crosses time while simultaneous courses are experienced)
- Extra-curricular (e.g., orientation)
- Required or Optional
- Elective or Selective
- CIWG Decision:
- Request #18: No Change. Integration blocks will remain. Consideration for changes to what they are called will be considered
- Request #19: No Change. Consideration for change to “course.” Similar to previous changes to other element naming conventions, marketplace impact of change compared to improved documentation should be heavily weighed.
- Attribute list to replace “ClerkshipModel” still under consideration.
- Current: For the item “competency object reference,” the description reads:
- A reference to the unique id for a learning objective, competency, learning outcome, (all of which are known as competency objects) associated with this event. CompetencyObjectReference has the following format: /CurriculumInventory/
- Proposed: Change the word “event” to “sequence block,” as this is a typo.
- Purpose: Clarity in the document(s) will help users better understand the specifications.
- CIWG Decision: Fix typo.
Revision request #25: Events in nested sequence blocks; Page number 47
- Current state: Sequence blocks are required to have at least one event in a CI data submission. With nested sequence blocks, these do not necessarily each need evets within them, if ultimately the nesting ends in at least on event.
- Proposal for change: Update description so that its clear eventually the nested sequence blocks need to have at least one event. “The parent block does not need to contain events.”
- CIWG Decision: Simple update to text to clarify description.
Revision request #26: Event reference; Page number 49