Begin testing with one piece of curriculum
Once you have access to CI Staging, it may be helpful to test upload one piece of your curriculum (e.g., one course), to see which (if any) standards or business rules are not met. You do not necessarily have to take this approach – you could upload your entire curriculum in CI Staging as well. This approach is recommended simply because it allows you to identify possible errors on a small scale, so you could have them addressed universally before the rest of the curriculum is also documented.
As long as the one piece of curriculum you are test-uploading meets the standards and business rules, it can be uploaded to CI Staging and generate a Verification Report. You can then review the Verification Report to ensure the data populated the tables as expected, to represent your curriculum accurately and completely.
Access the CI MedBiq standards and the CI Business Rules
The earliest you can test one piece of your curriculum in CI Staging would be once you have content from chapters 1-9 of this guidebook (Getting Started, Where Will Your CI Data Live and Thrive?, Program Objectives Drive Curriculum, Determining Your CI Organizational Strategy, Course-Level Details for Your CI, Maintaining and Using Your CI from Year to Year, Documenting Time, Event Learning Objectives, Instructional Methods, Assessment Methods, And Resources) for a portion of your curriculum. If you were to try to test upload only your program objectives from Chapter 3, for example, you would encounter standard and business rule errors because your CI data file would be missing content from courses and events.
Test uploading your data in CI Staging is not required, however, is highly recommended. If your school were to wait until the CI Portal opens August 1 to test your data, it may not leave sufficient time to correct any errors before the CI Portal closes on October 21.
Test upload your curriculum (e.g., one course) in CI Staging.
Technical specifications and business rules
Recall in Chapter 1 you explored the CI technical components on our Resources for CI Developers webpage. The MedBiquitous CI and competency framework specifications govern the structure and content of CI data. The AAMC CI Business Rules add caveats to the specifications, such as limitations on word counts. It is helpful to read those documents in that order.
Keep in mind that if you are using a CI participating vendor, rather than an institutionally developed system, your vendor also has access to CI Staging and may be able to assist you. More information about vendor access to CI Staging and expectations around their usage are described in the CI Portal User Guide.
Access the CI participating vendor list
If the file you test upload to CI Staging does not meet the MedBiquitous CI and competency framework specifications, CI Staging will not allow you to progress to the next phase (e.g., testing your data file against the AAMC CI Business Rules).
Once the MedBiquitous technical specifications are met, CI Staging will vet your CI data file (in XML) against the business rules. If any business rules are not met, an error report will be generated describing the errors which occurred. You can then edit your CI data file in your technical platform and try uploading a new CI data file. Once you are able to resolve the technical specification and business rule errors, you can add more curriculum to your test file so that eventually the entire curriculum is included in your test upload.
Once both the standards and business rules are met, a Verification Report is generated. It is normal to encounter technical specification and business rule errors that need to be resolved in the upload process. Even schools who have been uploading to the AAMC CI for years encounter errors due to technical platform enhancements, specifications and business rules evolution, and more importantly, adjustments and improvements in curriculum content and documentation practices.
Review the technical specifications and business rules and resolve any errors. Upload a new CI data file until all the standards and business rules are met, and the Verification Report populates accurately and completely to represent your entire curriculum.
Chapter 11 key questions
- Do all our key faculty and staff regarding the CI have access to the CI Portal and CI Staging as needed? Have we all read the CI Portal User Guide, and understand the purpose, functions, and differences between the CI Portal and CI Staging?
- Have we identified a piece of our curriculum we want to test, which has content documented from chapters 1-9 at minimum, from the Building a Curriculum Inventory Guidebook?
- Have we communicated with our IT staff and/or vendor to explain our goals and timeline for testing CI data in CI Staging, prior to the upload beginning August 1?
- Have we reviewed the technical specifications and business rules on the Resources for CI Developers webpage?
- Have we resolved any errors in our data file? Have we added additional curriculum to test so that have a CI data file that meets the technical specifications and business rules, and accurately and completely represents our curriculum?
- Are our Verification and Accreditation Support Reports populating as expected? Are there any blanks or missing data we need to address?
Log in to the Curriculum Community for additional resources, peer-to-peer conversations, and get your questions answered.
ACCESS PAST CHAPTERS OF THE BUILDING A CURRICULUM INVENTORY GUIDEBOOK