Venkatesh Chellappa
    • Create new note
    • Create a note from template
      • Sharing URL Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Customize slides
      • Note Permission
      • Read
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Write
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Engagement control Commenting, Suggest edit, Emoji Reply
    • Invite by email
      Invitee

      This note has no invitees

    • Publish Note

      Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

      Your note will be visible on your profile and discoverable by anyone.
      Your note is now live.
      This note is visible on your profile and discoverable online.
      Everyone on the web can find and read all notes of this public team.
      See published notes
      Unpublish note
      Please check the box to agree to the Community Guidelines.
      View profile
    • Commenting
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
      • Everyone
    • Suggest edit
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
    • Emoji Reply
    • Enable
    • Versions and GitHub Sync
    • Note settings
    • Note Insights
    • Engagement control
    • Transfer ownership
    • Delete this note
    • Save as template
    • Insert from template
    • Import from
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
    • Export to
      • Dropbox
      • Google Drive
      • Gist
    • Download
      • Markdown
      • HTML
      • Raw HTML
Menu Note settings Versions and GitHub Sync Note Insights Sharing URL Create Help
Create Create new note Create a note from template
Menu
Options
Engagement control Transfer ownership Delete this note
Import from
Dropbox Google Drive Gist Clipboard
Export to
Dropbox Google Drive Gist
Download
Markdown HTML Raw HTML
Back
Sharing URL Link copied
/edit
View mode
  • Edit mode
  • View mode
  • Book mode
  • Slide mode
Edit mode View mode Book mode Slide mode
Customize slides
Note Permission
Read
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Write
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Engagement control Commenting, Suggest edit, Emoji Reply
  • Invite by email
    Invitee

    This note has no invitees

  • Publish Note

    Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

    Your note will be visible on your profile and discoverable by anyone.
    Your note is now live.
    This note is visible on your profile and discoverable online.
    Everyone on the web can find and read all notes of this public team.
    See published notes
    Unpublish note
    Please check the box to agree to the Community Guidelines.
    View profile
    Engagement control
    Commenting
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    • Everyone
    Suggest edit
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    Emoji Reply
    Enable
    Import from Dropbox Google Drive Gist Clipboard
       owned this note    owned this note      
    Published Linked with GitHub
    Subscribed
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    Subscribe
    # Documents check-list for Autoseq CE-IVDR certification ## 1. Quality Management System (QMS) Documentation: ### Quality Manual: A document that describes your organization's quality management system and how it complies with the CE-IVDR requirements. ### Standard Operating Procedures (SOPs): Documented procedures for various processes within your organization, including development, testing, validation, and maintenance of the autoseq pipeline. #### Some of the SOPs that will be included in a bioinformatics QMS include: **Data management:** SOPs for data collection, storage, backup, and archiving to ensure data integrity and accessibility. This will include procedures for data curation, versioning, and data sharing with other researchers. **Quality control:** SOPs for quality control and validation of data, including procedures for data cleaning, error checking, and data formatting. This will include procedures for data validation, data quality assurance, and data quality control. **Analysis:** SOPs for bioinformatics analysis, including procedures for sequence alignment, gene expression analysis, and other bioinformatics workflows. This will include procedures for data analysis, data processing, and data interpretation. **Software and hardware:** SOPs for software and hardware installation, maintenance, versioning on git and management to ensure that all systems are up to date and working properly. This will include procedures for software installation, software validation, and software maintenance. **Data security:** SOPs for data security and access control, including procedures for data encryption, access permissions, and data sharing. This will include procedures for data security, data protection, and data privacy. **Compliance:** SOPs for compliance with regulatory requirements, including procedures for data governance, data integrity, and data security. **Auditing:** SOPs for internal and external auditing of data, analysis, and other bioinformatics processes to ensure compliance with regulatory requirements and the organization's policies. **Training:** SOPs for training of personnel on bioinformatics QMS processes, procedures, and compliance requirements. ## 2. Design and Development Documentation: ### Software Requirements Specification (SRS): A detailed document that specifies the functional and non-functional requirements of the software. ### Software Architecture Design: Detailed design documentation that describes the software's architecture, components, and interfaces. ### Risk Management Plan: Documentation outlining how you identify, assess, and mitigate risks associated with software development and usage. ### Traceability Matrix: A document that shows the relationship between the requirements, design elements, and test cases, demonstrating full traceability. ## 3. Validation and Verification Documentation: ### Validation Plan and Report: Documents outlining how you plan and execute the validation process to ensure the software performs as intended. ### Verification Plan and Report: Documents outlining how you plan and execute the verification process to ensure the software meets its specified requirements. ### Test Protocols and Test Reports: Detailed test plans and reports for various testing phases, including unit testing, integration testing, system testing, and user acceptance testing. ## 4. Regulatory Compliance Documentation: ### CE-IVDR Conformity Assessment: Documentation demonstrating how your software complies with the CE-IVDR requirements. ### Technical File: A compilation of all documentation, including design, validation, and risk assessment, required to demonstrate compliance with CE-IVDR. ### Declaration of Conformity: A formal document declaring your product's compliance with CE-IVDR regulations. ## 5. Change Control and Version Management: ### Change Control Procedures: Documentation outlining how changes to the software are managed, including versioning, testing, and validation of changes. ### Release Notes: Documentation detailing the changes made in each software release. ## 6. User Documentation: ### User Manuals: Manuals or guides for end-users explaining how to install, configure, and use the autoseq pipeline. ### Training Materials: Documentation for training end-users and operators. ## 7. Audit Trail and Logging Documentation: ### Audit Trail Records: Documentation of all actions taken within the software, including user access and system events. ### Logging Procedures: Documentation outlining how logs are generated, stored, and reviewed for compliance and troubleshooting. ## 8. Complaint Handling and Adverse Event Reporting: ### Complaint Handling Procedures: Documentation on how user complaints and issues are handled and investigated. ### Adverse Event Reporting: Procedures for reporting adverse events or incidents related to the use of the autoseq pipeline. ## 9. Data Security and Privacy Documentation: ### Data Protection Impact Assessment (DPIA): Documentation outlining how you assess and mitigate risks related to data protection and privacy. ### Security Measures: Documentation of security measures in place to protect user data and the pipeline itself. ## 10. Maintenance and Support Documentation: ### Maintenance Plans: Documentation outlining how you plan to maintain and update the software. ### Support Procedures: Documentation describing how support requests are handled and resolved. ## 11. Records and Document Control: ### Document Control Procedures: Procedures for creating, reviewing, approving, and maintaining documents. ### Record Keeping: Procedures for maintaining records of all activities related to the autoseq pipeline. ## 12. Training Records: ### Training Records: Records of training provided to personnel involved in the development, maintenance, and support of the autoseq pipeline. ## 13. Supplier and Subcontractor Documentation: ### Supplier Agreements: Documentation of agreements with suppliers or subcontractors, including software component suppliers. ## 14. Regulatory Submissions: ### CE-IVDR Submission Documents: Documents required for the CE-IVDR certification process, including the technical documentation required for review by a Notified Body. ### CAPA (Corrective and Preventive Actions) Documentation: CAPA Procedures and Records: Procedures for identifying, addressing, and preventing issues or non-compliance.

    Import from clipboard

    Paste your markdown or webpage here...

    Advanced permission required

    Your current role can only read. Ask the system administrator to acquire write and comment permission.

    This team is disabled

    Sorry, this team is disabled. You can't edit this note.

    This note is locked

    Sorry, only owner can edit this note.

    Reach the limit

    Sorry, you've reached the max length this note can be.
    Please reduce the content or divide it to more notes, thank you!

    Import from Gist

    Import from Snippet

    or

    Export to Snippet

    Are you sure?

    Do you really want to delete this note?
    All users will lose their connection.

    Create a note from template

    Create a note from template

    Oops...
    This template has been removed or transferred.
    Upgrade
    All
    • All
    • Team
    No template.

    Create a template

    Upgrade

    Delete template

    Do you really want to delete this template?
    Turn this template into a regular note and keep its content, versions, and comments.

    This page need refresh

    You have an incompatible client version.
    Refresh to update.
    New version available!
    See releases notes here
    Refresh to enjoy new features.
    Your user state has changed.
    Refresh to load new user state.

    Sign in

    Forgot password

    or

    By clicking below, you agree to our terms of service.

    Sign in via Facebook Sign in via Twitter Sign in via GitHub Sign in via Dropbox Sign in with Wallet
    Wallet ( )
    Connect another wallet

    New to HackMD? Sign up

    Help

    • English
    • 中文
    • Français
    • Deutsch
    • 日本語
    • Español
    • Català
    • Ελληνικά
    • Português
    • italiano
    • Türkçe
    • Русский
    • Nederlands
    • hrvatski jezik
    • język polski
    • Українська
    • हिन्दी
    • svenska
    • Esperanto
    • dansk

    Documents

    Help & Tutorial

    How to use Book mode

    Slide Example

    API Docs

    Edit in VSCode

    Install browser extension

    Contacts

    Feedback

    Discord

    Send us email

    Resources

    Releases

    Pricing

    Blog

    Policy

    Terms

    Privacy

    Cheatsheet

    Syntax Example Reference
    # Header Header 基本排版
    - Unordered List
    • Unordered List
    1. Ordered List
    1. Ordered List
    - [ ] Todo List
    • Todo List
    > Blockquote
    Blockquote
    **Bold font** Bold font
    *Italics font* Italics font
    ~~Strikethrough~~ Strikethrough
    19^th^ 19th
    H~2~O H2O
    ++Inserted text++ Inserted text
    ==Marked text== Marked text
    [link text](https:// "title") Link
    ![image alt](https:// "title") Image
    `Code` Code 在筆記中貼入程式碼
    ```javascript
    var i = 0;
    ```
    var i = 0;
    :smile: :smile: Emoji list
    {%youtube youtube_id %} Externals
    $L^aT_eX$ LaTeX
    :::info
    This is a alert area.
    :::

    This is a alert area.

    Versions and GitHub Sync
    Get Full History Access

    • Edit version name
    • Delete

    revision author avatar     named on  

    More Less

    Note content is identical to the latest version.
    Compare
      Choose a version
      No search result
      Version not found
    Sign in to link this note to GitHub
    Learn more
    This note is not linked with GitHub
     

    Feedback

    Submission failed, please try again

    Thanks for your support.

    On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

    Please give us some advice and help us improve HackMD.

     

    Thanks for your feedback

    Remove version name

    Do you want to remove this version name and description?

    Transfer ownership

    Transfer to
      Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

        Link with GitHub

        Please authorize HackMD on GitHub
        • Please sign in to GitHub and install the HackMD app on your GitHub repo.
        • HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.
        Learn more  Sign in to GitHub

        Push the note to GitHub Push to GitHub Pull a file from GitHub

          Authorize again
         

        Choose which file to push to

        Select repo
        Refresh Authorize more repos
        Select branch
        Select file
        Select branch
        Choose version(s) to push
        • Save a new version and push
        • Choose from existing versions
        Include title and tags
        Available push count

        Pull from GitHub

         
        File from GitHub
        File from HackMD

        GitHub Link Settings

        File linked

        Linked by
        File path
        Last synced branch
        Available push count

        Danger Zone

        Unlink
        You will no longer receive notification when GitHub file changes after unlink.

        Syncing

        Push failed

        Push successfully