CorpusRecord 76077

Residency in ECOS Webinar

A searchable transcript preserved as part of the Discourse Corpus. Passage numbers provide stable references within this record; verify quotations against the original recording when available.

Source
YouTube / Texas Education Agency
Date
2024-12-18
Location
McLennan County, TX
Material
Transcript
Extent
3,386 words · about 19 min
Collected
2026-06-08

Transcript

Verbatim source text

001all right good afternoon thank you for joining our webinar on residency in EOS uh we aim to cover everything thoroughly but we do understand you may have additional questions so please record your questions in the chat and we'll respond through FAQs or personal communication after the webinar the webinar is being recorded and the recording along with related FAQs will be available in the EP training events and material sections on the program provider resources page on the tea website this presentation is applicable to EPS who have completed the application process through tea and have been approved by the ESC to offer the Texas teacher residency preparation route which I will refer to as residency for the remaining of this presentation today through the application and approval process your EP has demonstrated they understand the residency requirements

002and have structures in place for candidates to meet the residency requirements that will qualify them to receive the enhanced standard certificate so we will not be covering residency rules during the presentation I've listed key elements of the residency requirements here because because the EOS updates we are about to review are based on and aligned with the residency requirements in Texas administrative code some of the TAC aligned ecos updates we will discuss today are around um excuse me someone else is trying to join some of the tack aligned EOS updates we will discuss today are around identifying residency as a def root capturing evidence of requirements met during the clinical experience and validating issuance of the enhanced standard certificate against requirements met support for reporting activity around the residency route also meets ASAP requirements as a

003reminder ASAP is a term for the accountability system for Education educator preparation programs Texas Education Code Tech and Texas administrative code Tech require educator preparation programs EPS to support specific information and data to the state annually which we will refer to annual ASAP reporting or state reporting the data reported by EPS is used for a variety of purposes among those is to determine annual accreditation status for eps note that ASAP also happens to be the name of one of the drop-down menus in the Eos for entities green screen some of the residency updates we will review today are under that ASAP menu if you are new to the EP and you want to learn more about ASAP and the related calculations there is an ASAP manual published as a figure in Tac 2291 C that

004you may want to review remember that each program within the EP contributes to the data collected each year and this includes residency programs so effective communication across the programs is vital for efficient and accurate data collection and Reporting processes for the EP as we cover this information if you have questions please put them in the chat we will include them in an FAQ to be posted soon again the webinar is being recorded and the recording along with related FAQs will be available in the EP training events and manual uh materials section on the program provider resources page on the tea website let's review some relevant terms that I'll be referencing throughout this presentation first as we all know EP is the educator preparation program which you are are here representing today EOS is the educator

005certification online system which houses the educator data Statewide including the data reported by EPS the focus of this presentation today is the updates that have been made in EOS to support residency routs te Aid is the identification number assigned to candidates and the Educators that it is used for certification and the exam registration process the term clinical experience broadly describes clinical teaching internship practicum and effective 91 2024 includes the ASC approved residency data reporter is a role that may be referenced today if an EP has a person whose function is specifically to report data each year that person would be considered the data reporter whoever completes the state reporting for your EP must have the ASAP upate access in EOS for entities and this includes reporting residency data since some of the updates are under

006the ASAP dropdown menu if you have new staff that need assistance establishing the correct accesses and EOS entities please have them reach out to your assigned specialist at tea for that assistance and finally when we referred to residency we referring to the espc approved route that results in enhanced standard certificate our goals for this presentation are first to provide an overview for the ESC approved residency programs on how to process your residency candidates in EOS and identify some resources available to you for help should you need it additionally I'll let you know about some EOS updates that are forthcoming in the next few months this is also an opportunity for you to gather your thoughts and questions around residency data reporting and then submit those questions to tea so we can provide Clarity we will

007publish responses for the good of the group please ask and we will respond While most screens and functions in ecos have not been changed you will see residency related additions throughout the screens the presentation today will highlight these new features you will see that there is a new root code for residency and new cert license IDs for the teaching certificates offered in The Residency route which are integrated through out existing screens including admissions finisher records list test approval clinical experience records and observations additionally we've updated the clinical experience screens to capture residency data and have added new screens to capture performance Gates data The Residency updates in EOS are not complete but are on target to be completed we will review the remaining expected updates later in this presentation now let's move into EOS and

008view the updates related to residency reporting today we are welcoming awesome educator as a candidate recently admitted to your EP participating in the espc approved Residency program awesome educator may be a familiar candidate to you as many of the screens you will see today are also in the updated technical manual as with all new candidates admitted to EPS awesome needs an admission record created in EOS the process of creating the admission record has not changed and the screens have not changed the record may be created through the manual or upload process which is current functionality The Residency route has been integrated in into the admission screens just as a reminder there is a requirement in 19 Tech 22717 that the admission record must be created within seven calendar days of the formal admission date for

009each candidate please note if your candidate is already admitted into your EP and is later moved into the residency route you would not create a new admission record for that candidate we will address that transition later there are three screens under the aset menu that EPS use to create and track admission records for candidates you'll find more information about how to navigate and use these screens in the data reporting manual the screenshot on this slide depicts an emission report you can access via maintain admissions select the 2024 2025 reporting year to generate the report of all admission records created for 2425 you can also export the report in an Excel file that will allow you to sort your residency candidates will appear on this report note that admission records cannot be deleted by an EP

010which which is existing functionality if you create the record in error send a written request to your assigned specialist via the tea help desk directing us to remove the record for you the admission record should not be deleted or changed if the candidate leaves the EP after admission or changes certification categories the candidate's admission in the original category remains unchanged despite any subsequent changes to the candidate's status or certificate area I'm using the manual option to create a mission record for awesome the upload option is available as well for those who want to use it notice the new residency route has a code of 47 this will be the root code you will select when created admission records for candidates who are admitted into the espc approved residency route When selecting the certificate please make

011sure the certificate area is coded with the RSD at the end of the certificate note that only those certificates identified in your aspec approval will be available for The Residency route please be mindful that a new cert license ID has been generated for the RSD coded certificates so if you are accustomed to selecting let's say seert id1 1990 for undergraduate candidates pursuing core subjects EC through 6 you will now select CT license ID 2340 for residency route candidates pursuing core subjects EC through six note that CT ID codes are unique to the root meaning the core subjects EC through six CT ID code is different for the undergraduate the postback alternative and residency Roots this is existing functionality The Residency route being the new addition I'm going to complete Awesome's admission record as usual by

012populating the information about admission date GPA data and data relating to subject specific credit hours this is also existing functionality which has not been changed candidate enrollment data must be reported by the EP this reporting requirement has been in effect since 200920 reporting year before that only finishers were reported candidate enrollment records are reported on the finisher records list in EOS The Finisher records list is one list that can be sorted for all candidates or by enrollment status of other enrolled or finisher you can also display those candidates removed from the list for your convenience when you create the admission record for a candidate EOS creates the enrollment record for the candidates for each of the certificates included in the admission record the enrollment status is automatically populated as other enrolled the admission record also

013creates a test approval record for the candidate the candidate's status will be marked as eligible because the EP decides when the candidate is ready for testing and when to approve it you'll note that in both the finisher records list and the test approval screens The Residency route will be reflected if that is the route you identified at admission it is always good practice to verify records were created after the admission was created one way to do this is to click on maintain finishers then use the status filter set to other enrolled or all in the current reporting year notice Awesome's en enrollment record is present and note that the record reflects the RSD or residency route if a candidate was admitted into a different route and then transfers into the residency route you would update

014the route here you can do so by pulling up the student maintenance screen via student search adding the new residency certificate and then removing the previous certificate note again that only the certificates that are approved for your residency program may be added you can also verify that test approvals were created by the admission record by searching in your test menu use search maintain candidates under the test approval drop down menu to find the candidate and view the test approvals this is existing functionality and is not new if you need to add a test approval you can still do so using the existing functionality I wanted you to see that the RSD 47 route is now an option in this screen as well as a reminder candidates completing espc approved residency programs will still need to

015take their content exams St Str exam if applicable and any supplemental exams as applicable but they will not be required to take the Ed TPA or PPR exam clinical experience records enable the EP to efficiently record essential information regarding clinical experiences which now includes residency for those approved by the espc to offer that route EPS are obligated to Monitor and document activities around clinical experiences note that candidates must have an admission record and must have an enrollment record on the finisher records list before the EP can create the clinical experience records for the candidates additionally candidates must have a clinical experience record for an EP to be able to report the related observations this is all existing functionality that was not changed any candidate in a program within the EP who completes a clinical experience

016or who is exempt from a clinical experience must have a clinical experience record there are two screens under the ASAP drop-down menu in ecos that allow the EP to create and manage clinical experience records EPS can create a clinical experience record for an individual candidate manually via the clinical experience records option or for one or more candidates using the bulk upload via the upload clinical experience option this was existing functionality and it is not new now awesome is ready to begin the full year residency so I will create the clinical experience record using the manual option to do so I search on awesome uh Awesome's teid number and then selected the ad record to report the ESC approved residency I used the 750 hours ASPC approved residency model for the clinical teaching or Clint assignment

017type I also selected Awesome's C certificate area as the RSD root option I can verify the record by using the clinical experience records option to generate and view a report of all clinical experience records created for that year awesome should have an record there now that I've created it note there is limited editing and deleting allowed for clinical experience records for example once a record is tied to an observation the EP cannot edit or delete that record in the interest of accurate data if an EP staff need assistance with correcting these records please reach out to the assigned specialist at tea due to recent enhancements in our admin screens we may be able to make a correction for you data around field supervision is another important area that you must report including for candidates completing

018the residency EPS must report all formal observations conducted by field supervisors the number of formal observations for the candidate must meet or exceed the minimum number of required observations for the clinical the type of clinical experience in which the CL the candidate participated the observation requirements are existing and are also applicable to residency candidates it is very important that 's report all observations for all candidates who are in any part of a clinical experience during a reporting year since observation completion is part of indicator 4 of the EP accountability indicators identified in 19 Tech 229.5 now here's an important note informal observations conducted by the field supervisor and any observations conducted by cooperating teachers mentors campus supervisors site supervisors or host teachers are not reported in EOS retain the evidence of informal observations and coaching

019conducted by field supervisors and campus Personnel in candidates records as part of the completion documents required to kept per the records retention requirement in 19 Tac 22813 this chart is linked in the observation upload screen and is meant to be a quick reference only the actual requirements for observations are in 19 Tac chapter 228 sub chapter F related to support for candidates during required clinical experiences this chart provides an example of the number and format of formal observations that you would be expected to report in aset based on the clinical experience in which the candidate is engaged note the second column if the EP chooses to conduct formal observations in person only the minimum number of formal observations required for candidates seeking one certificate category is listed however if the EP chooses to conduct formal

020observations in person and virtually the combinations of minimum formal observations allowed per setting is listed in column three it is very important to note that all formal observations of residency candidates must be in person if your EP allows virtual operation uh observations to be conducted for the teacher candidates in other routes besides residency tea strongly encourages you to communicate with field supervisors about the rules around in-person versus virtual observation requirements including the in-person requirement for residency candidates for all programs and not just residency a field has been added to the screen used to create observation records manually this enhancement requires you to choose the correct experience model this must be entered to save an observation manually this enhancement was added to the manual screen for cases where a candidate has multiple experience records EPS were

021reporting trouble with the entering data when multiple experience records existed with common dates this enhancement to the manual screen ensures EPS can correctly assign the observation to the correct clinical experience record I've selected the 750 hours option for awesome because awesome is a candidate in The Residency route Note The Experience model is not required in the upload screen though if you have candidates with overlapping dates on clinical experiences such as may happen for extensions you will use the manual screen to enter observations for that candidate thus far we've reviewed EOS screens that are existing and have been enhanced with the residency route now we'll look at a new screen that's been created specifically for The Residency route this is the interface where EPS will enter evidence that candidates met each performance gate requirement there are

022two new screen options under the ASAP drop-down menu for managing performance Gates data the performance Gates option allows you to view a report of all candidates and their progression through performance Gates and allows you to manually create a performance gate record by searching on the tea ID number of the candidate additionally there's an upload screen that allows for bulk upload of the performance gate data for multiple candidates this screenshot shows that the functionality of the screen in the performance Gates option is similar to functionality in the clinical experience record option we hope you find this to be a userfriendly approach to the uh EOS enhancements awesome educator has now progressed through that first performance gate so I need to record it in EOS in the previous slide I entered awesome T Awesome's tea ID number

023to find the record and then when no record was found I clicked on ADD record to generate this manual data entry screen note that performance gates are recorded as the date the perent performance level measure in each Dimension was met and that there must be a total of four to complete this portion of the candidate's record there is no need to upload the actual performance gate document such as the pop cycle or dispositional survey the EP is only attesting to the candidate demonstrating proficiency and the date no actual documents are being uploaded there are some validations built in to help keep your data clean first you must enter performance gate one to be able to generate a record second each performance gate record must reflect a date that is sequentially later than the date in

024the previous performance gate this structure is based on the requirement that performance Gates reflect a progression of Mastery throughout the experience and third performance gate dates must be within the assignment begin and end dates this validation is similar to Observation validation which requires observation dates to be within assignment begin and end dates entering and saving Awesome's first performance gate generated a record that I can now find by searching Awesome's tea ID from this screen I can use the pencil icon to add performance Gates manually as they are met and I can review all performance Gates on this record to verify they're complete as with other options in ecos I can always add the performance gate data via upload as well when awesome meets the next performance gate I'll simply add that date and save the

025record I can do this via upload as well all four performance Gates must be met before awesome can be considered a finisher in The Residency route so today we've reviewed the updates and news screens for processing residency candidates through admissions enrollment records test approvals clinical experiences and related obervations and performance Gates we have not reviewed the screens for recommending enhanced certificate standard certificate because those updates to EOS are still in process they're expected after the first of the year we will post a notice in the EP newsletter when those screens have been implemented in ecos there will also be related updates added to the technical manual on using those screens however functionality will be very similar to that that you are already using in the standard certificate recommendation screen I wanted to mention this now

026because there are some aspects of the enhanced standard certificate recommendation that are new and you do need to know what those are uh now to be prepared for them when you eventually recommend your enhanced standards as in Tac issuance of of the enhanced standard certificate is based on candidates meeting specific criteria in The Residency route the validations built into the enhanced standard recommendation screens are based on those requirements when you recommend the enhanced standard the candidate must be identified as a finisher on the finisher records list in The Residency route and the candidate must have all four performance Gates requ recorded in EOS if these two requirements are not met when you recommend the certificate you will get an error message and the certificate will not issue issuance will also require a degree to be

027entered which is not new functionality and currently exist in the certificate recommendation screens it is important for you to know this now so you can begin with the end in mind regarding your recordkeeping as we always recommend enter your data as you go throughout the year this will be important for trouble-free recommendations of enhanced standard certificates for your residency candidates we hope that you find this presentation to be helpful there are other resources available to you if you need the data reporting manual Remains the best resource for EP staff with detail and instruction around required reporting including useful examples and screenshots throughout the manual you will find the most recent version of the data reporting manual posted in the forms and documents section on the program provider resources web page on the tea website as

028new functionality is introduced the manual is updated accordingly Additionally the Weekly Newsletter will contain reminders and information related to EOS updates as well as contact information for various tea staff who can assist you to subscribe to the newsletter use the link at the top of the most recent archived copy of the newsletter the archives are also on the program provider resources page for the most efficient service when you need assistance related to EOS functions please use the tea help desk system this process is prepared because the help desk is monitored by multiple tea staff ensuring your submission won't get lost and will get routed to the correct person who can best address your questions or problems Additionally the help desk is secure so if you must Sim files that contain candidate identifiers you you can

029do so with confidence a reminder that you've heard before that if you need to submit a file for review please help us by labeling your files with a short specific names submit forms and inquiries to the data reporting tile no need to identify your or to notify your educational specialist separately as the help desk uh system will automatically send us an email when your ticket arrives now that your EP has been approved by the ESC to offer The Residency route you will see the enhancements discussed today when EOS is updated soon you will receive notification that The Residency Fields have been installed for your EP and that all espc approved residency root certificates have been added to your inventory as discussed earlier please monitor the newsletter for more EOS related updates regarding residency to follow

030in the coming months and as always report your data throughout the year waiting until candidates are ready to be recommended for an enhanced standard certificate could delay the certification process while this concludes our training on The Residency updates in EOS please record your final questions in the chat give us a few days to get the recording of this presentation posted as well as the FAQs we'll notify you in the newsletter when the recording is posted I hope you have a wonderful day and best wishes for an efficient and trouble-free ttrp data reporting experience

This transcript may contain errors introduced by automated or source-provided captioning. Bracketed descriptions such as [Music] are retained from the source. Passage divisions are editorial aids and do not alter the wording.