Training activity information

Details

Submit data to the HFEA

Type

Entrustable training activity (ETA)

Evidence requirements

Evidence the activity has been undertaken by the trainee repeatedly, consistently, and effectively over time, in a range of situations. This may include occasions where the trainee has not successfully achieved the outcome of the activity themselves. For example, because it was not appropriate to undertake the task in the circumstances or the trainees recognised their own limitations and sought help or advice to ensure the activity reached an appropriate conclusion. ​

Reflection at multiple timepoints on the trainee learning journey for this activity.

Considerations

  • HFEA regulations
  • Data validation and reporting
  • Timely and accurate submission
  • Published HFEA data

Reflective practice guidance

The guidance below is provided to support reflection at different time points, providing you with questions to aid you to reflect for this training activity. They are provided for guidance and should not be considered as a mandatory checklist. Trainees should not be expected to provide answers to each of the guidance questions listed.

Before action

What does success look like?

  • Identify what is expected of you in relation to data submission, for example, ensuring all required fields for treatment outcomes are accurately transcribed into the HFEA submission portal.
  • Consider how the learning outcomes apply, specifically how correct data submission ensures you are practicing in accordance with the statutory and regulatory framework and HFEA reporting requirements.
  • Discuss with your Training Officer to gain clarity of what is expected of you in relation to the specific procedures and deadlines for submitting treatment and outcome data.

What is your prior experience of this activity?

  • Think about what you already know about data management, quality control, or using online submission systems. Have you worked with the type of clinical or laboratory data that needs to be reported to the HFEA before?
  • Consider possible challenges you might face during the activity, such as identifying data errors, technical issues with the submission portal, or ensuring data completeness from various sources, and how you might handle them.
  • Recognise the scope of your own practice for this activity i.e. know when you will need to seek advice or help, and from whom. You will need to seek advice from your Training Officer when required, for example, if a discrepancy exists between the internal database and the data required for submission, or if the submission portal is unavailable.
  • Acknowledge how you feel about embarking on this training activity, particularly concerning the importance of accuracy and compliance when submitting regulatory data.

What do you anticipate you will learn from the experience?

  • Consider the specific skills you want to develop, such as data verification, using the HFEA reporting interface, understanding data definitions and requirements specified by the HFEA, and adhering to strict processes.
  • Identify the specific insights you hope to gain from engaging with the activity, such as a deeper understanding of the HFEA’s role in monitoring treatment outcomes and practice, and the importance of data integrity for regulatory oversight.

What additional considerations do you need to make?

  • Consult actions identified following previous experience with data handling or regulatory reporting.
  • Identify important information you need to consider before embarking on the activity, such as the specific type of data being submitted (e.g., treatment cycles, outcomes), the HFEA’s specific reporting guidelines, and the clinic’s internal process and timeline for preparing data for submission.

In action

Is anything unexpected occurring?

  • Are you noticing anything surprising or different from what you anticipate whilst submitting data to the HFEA?
  • Are you encountering situations such as:
    • The online submission system presenting an error message or behaving unexpectedly?
    • A data validation check failing for reasons you didn’t anticipate?
    • Suddenly realising that a crucial piece of information was missing or potentially incorrect in the dataset?

How are you reacting to the unexpected development?

  • How is this impacting your actions? For example, are you responding to the situation appropriately? Are you immediately stopping the submission process?
  • Consider the steps you are taking in the moment, such as attempting to troubleshoot the system error or seeking immediate help from a colleague.
  • How are you feeling in that moment? For instance, are you finding it difficult to troubleshoot the issue? Is it affecting your confidence in completing the submission accurately and compliantly?

What is the conclusion or outcome?

  • Identify how you are working within your scope of practice. For example, did your immediate action prevent potential submission of incorrect data, thus maintaining compliance? Or are you needing support because the system error or data conflict requires senior technical input before the statutory report can be finalised?
  • What are you learning as a result of the unexpected development? For example, are you gaining insight into potential pitfalls or checks to perform while submitting data to the HFEA?

On action

What happened?

  • Begin by summarising the key steps you took when submitting data, including the data you submitted and the process you followed to submit it to the HFEA.
  • Consider specific events, actions, or interactions which felt important, such as the key HFEA requirements you followed regarding data integrity and submission timelines.
  • Include any ‘reflect-in-action’ moments where you had to adapt to the situation as it unfolded, for instance, immediately double-checking the accuracy of a crucial data field when a system validation check warned of a potential transcription error.
  • How did you feel during this experience, e.g., did you feel responsible for ensuring regulatory accuracy or stressed by technical difficulties with the submission portal?

How has this experience contributed to your developing practice?

  • Identify what learning you can take from this experience regarding the process and importance of submitting data to the HFEA. What strengths did you demonstrate, e.g., accurate presentation and entry of quantitative data?
  • What skills and/or knowledge gaps were evident, e.g., unfamiliarity with the specific data definitions required for reporting certain outcomes?
  • Compare this experience against previous engagement with similar activities – were any previously identified actions for development achieved? Has your practice improved in adhering to data reporting obligations under the statutory and regulatory framework?
  • Identify any challenges you experienced, such as technical issues with the submission system or ambiguity in reporting requirements. Identify how you reacted to this, e.g., needing to seek advice or clarification on scope of practice regarding the required procedure for reporting an unavoidable data inaccuracy.

What will you take from the experience moving forward?

  • Identify the actions or ‘next steps’ you will now take to support the assimilation of what you have learnt, including from any feedback you have received, with regards to improving the robustness of your internal quality checks before submission.
  • What will you do differently next time you approach submitting data to the HFEA for example, ensuring you have all relevant data to hand.
  • Do you need to practise any aspect of the activity further, such as reviewing specific data definitions within HFEA guidance or key learning outcomes related to practicing in accordance with the statutory framework?

Beyond action

Have you revisited the experiences?

  • How have your subsequent experiences of submitting data to the HFEA since completing this specific training activity led you to revisit your initial approach or decisions during that activity? For example, how an instance where a subsequent submission required complex validation checks against HFEA data definitions forced you to re-evaluate the rigour of your quality control process during your first attempt at this training activity.
  • Considering what you understand about HFEA statutory reporting requirements, data integrity, and compliance now, were the actions or considerations you identified after your initial reflection on this training activity sufficient? How have you since implemented or adapted improvements in your data submission workflow based on further learning and experiences?
  • Has discussing data management issues or the regulatory consequences of inaccurate data submission with colleagues, peers, or supervisors changed how you now view your initial experience in this training activity? For example, how professional storytelling with a supervisor about an audit finding related to delayed or inaccurate reporting refined your understanding of the critical nature of practicing in accordance with the statutory and regulatory framework.

How have these experiences impacted upon current practice?

  • How has the learning from this initial training activity, in combination with subsequent HFEA data submission experiences, contributed to your overall confidence and ability in regulatory data submission and quality control, particularly in preparing for assessments like DOPS or OCEs? For example, how your accumulated precision in data verification and understanding of regulatory deadlines enables confident discussion of compliance and reporting processes during a Case-Based Discussion (CBD) assessment.
  • How has reflecting back on this specific training activity, combined with everything you’ve learned since, shaped your current approach to HFEA data submission? How does this evolved understanding help you identify when something is beyond your scope of practice or requires escalation? For example, how your evolved understanding helps you identify when system errors or conflicting data points require immediate escalation to the Training Officer or data governance lead before statutory reporting deadlines are missed, ensuring compliance with the statutory framework.
  • Looking holistically at your training journey, how has this initial HFEA data submission experience, revisited with your current perspective, contributed to your development in meeting the learning outcomes related to practicing in accordance with the statutory and regulatory framework? For example, how this foundational experience has supported your development in practicing in accordance with the statutory and regulatory framework by maintaining accurate data for public record and regulatory oversight.

Relevant learning outcomes

# Outcome
# 2 Outcome

Practice in accordance with the statutory and regulatory framework.