Version History definition

Version History. Date Developed: 12/1999; replaces policy of same name dated 5/03 Last Review/Revision: 12/2005, 2008, 10/2013, 5/2014, 6/2019, 8/2020 Legal Review: 7/2019, 8/2020 To define the requirements for Sponsoring Institution’s Statement of Commitment, inter-institutional affiliation agreements and program letters of agreement for the University of Arkansas for Medical Sciences College of Medicine (UAMS COM) and its Accreditation Council for Graduate Medical Education (ACMGE) sponsored residency programs.
View Source
Version History. Date Developed: 12/1999; replaces policy of same name dated 5/03 Last Review/Revision: 12/2005, 2008, 10/2013, 5/2014, 6/2019, 8/2020, 9/2021, 9/2022 Legal Review: 7/2019, 8/2020, 9/2021, 9/2022 To define the requirements for Sponsoring Institution’s (SI) Statement of Commitment, inter- institutional affiliation agreements and program letters of agreement for the University of Arkansas for Medical Sciences College of Medicine (UAMS COM) and its Accreditation Council for Graduate Medical Education (ACGME) sponsored residency/fellowship programs and ACGME Non-Standard Training programs.
View Source
Version History. Date Developed: 12/1999; replaces policy of same name dated 5/03 Last Review/Revision: 12/2005, 2008, 10/2013, 5/2014, 6/2019, 8/2020, 9/2021, 9/2022 Legal Review: 7/2019, 8/2020, 9/2021 To define the requirements for Sponsoring Institution’s (SI) Statement of Commitment, inter- institutional affiliation agreements and program letters of agreement for the University of Arkansas for Medical Sciences College of Medicine (UAMS COM) and its Accreditation Council for Graduate Medical Education (ACGME) sponsored residency/fellowship programs. organization (HMO), a medical examiner’s office, a consortium or an educational foundation.
View Source

Examples of Version History in a sentence

  • Accept Voucher XML from the NAVITAIRE reservation system and validate file, load to Temporary Database for further processing by Version History module.

  • Accept Credit Shell XML from the NAVITAIRE reservation system and validate file, load to Temporary Database for further processing by Version History module.

  • Accept Flight Following XML from the NAVITAIRE reservation system and validate file, load to Temporary Database for further processing by Version History module.

  • Accept PNR XML from the NAVITAIRE reservation system and validate file, load to Temporary Database for further processing by Version History module.

  • Accept PNR XML from the NAVITAIRE reservation system and validate file, load to Temporary Database for further processing by Version History module, • Voucher Load.

  • Version History Latest Version Please check for the latest version of this document by contacting the County’s Technology Services Department.

  • A.1. Version History 06.2010 1.0 Guardtime Creation of the document.

  • Any changes will be reflected through a change in the Procedure’s Version History and forwarded to the Distribution List set forth in Appendix 1.

  • Any amendment to this Exhibit A shall be in writing and transmitted to all Parties to the Agreements within seven (7) business days of the version change contained in the document Version History.

  • All amendments to this SOP shall be documented in the Version History section and published according to the practices described in Section 2, Review and amendment of existing SHIN-NY SOPs. NYeC will post or otherwise make the amended SOP available to the public.


More Definitions of Version History

Version History. The version history is provided for informational purposes and lists information regarding prior versions of the regional standard.
View Source
Version History button was expected but the data are listed in the tab “Files” 2) For the content administrator it is difficult to recognize which metadata were updated for each specific version. 1) Rename tab “Files” to “Version History”. 2) Mark with a different colour the metadata that were updated. The feature needs to be tested within the BF5 environment. 3 CS5 Import RF12- The archive can import METS BF5 Blogforever METS files supplied by CERN match the METS standards. None None 4 CS5 Image files RF67- The archive fetches and stores embedded content BF5 Media such as images that are contained in a blog post are ingested into the repository and are visible to the user under the tab "Files". These media files are stored within the repository and are viewable by a user. This feature is functional on some records, but not all. Ensure embedded media files from all records are fetched and stored in the repository. 3
View Source

Related to Version History

  • Dataset means the data specified in Appendix 1 (Environmental Information) to Schedule 11.2 (Management Information) as the same may be amended from time to time by the Secretary of State (acting reasonably);

  • Version means a release of software that contains new features, enhancements, and/or maintenance updates, or for certain software, a collection of revisions packaged into a single entity and, as such, made available to our customers.  Relocation and impact on Support. Relocation of any products under support is your responsibility and is subject to local availability and fee changes. Reasonable advance notice to HPE may be required to begin support after relocation. For products, any relocation is also subject to the license terms for such products.  Multi-vendor Support. HPE provides support for certain non-HPE branded products. The relevant data sheet will specify availability and coverage levels and the support will be provided accordingly, whether or not the non-HPE branded products are under warranty. HPE may discontinue support of non-HPE branded products if the manufacturer or licensor ceases to provide support for them.

  • template version has the meaning ascribed to such term in NI 41-101 and includes any revised template version of marketing materials as contemplated by NI 41-101;

  • Fluoroscopic imaging assembly means a subsystem in which X-ray photons produce a visual image. It includes the image receptor(s) such as the image intensifier and spot-film device, electrical interlocks, if any, and structural material providing linkage between the image receptor and diagnostic source assembly.

  • Compatibility means a condition in which land uses or conditions can coexist in relative proximity to each other in a stable fashion over time such that no use or condition is unduly negatively impacted directly or indirectly by another use or condition.