MOPCON
      • 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
        • Owners
        • Signed-in users
        • Everyone
        Owners Signed-in users Everyone
      • Write
        • Owners
        • Signed-in users
        • Everyone
        Owners 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
    • 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 Help
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
Owners
  • Owners
  • Signed-in users
  • Everyone
Owners Signed-in users Everyone
Write
Owners
  • Owners
  • Signed-in users
  • Everyone
Owners 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
    # AI?醫療?創業?的現在過去未來 - Frankie Chan {%hackmd MNcuRlXoQDak0uCmtaJKwA %} [TOC] > 和醫師合作的經驗分享 > 創業的歷程 > 醫療 AI ## 醫療 AI - 台灣的醫療水準和香港比較之下優渥 - 是不是可以透過 AI 加快醫療檢測的流程,有效提早治療疾病 - 依據醫學統計,女性平均二個人就有一個人終其一生就有就會得到一種癌症,男性為三個人就有一人 ## 人工智慧於癌症醫療之多面向 + 精準 + 治療 + 預後 + 管理 ## 參與比賽經驗 創新醫療的挑戰度高 因為醫療流程冗長 1. 前處理期 + *IRB審核 2. 模型建置與測試 3. 醫材登記與上市 + 器材臨床實驗 + FDA醫材登記 ## 醫療影像的技術 ### 癌症治療三支柱 - 手術治療 - 放射治療 - 透過放射線去殺死細胞 - 藥物治療 ### 智慧放療 AI 系統 > 透過人工智慧技找到患處進行治療 > 放射治療室最適合做 AI (因爲有影像判讀的部份) #### 需要和既有的系統與硬體廠商進行深度整合 從臨床出發,找出醫療影像的應用需求 智慧放療 AI 系統整合的系統,包含: + viewray + elekta + varian + accuray #### CT 是什麼? > 電腦斷層掃描,是一種影像診斷學的檢查,非侵入性的檢查,檢查的結果影像不僅可以顯現正確位置、大小, 更可以藉由數字表現體內的組織狀態。 >CT無法像一般影像的方式進行處理 因為CT的pixel代表的材質不同,例如:骨頭、肌肉, etc. ## AI 影像判斷勾畫 透過影像辨識技術可以更精確的在醫療影像上精確的繪出癌症位置。 > 使用 影像辨識技術的Image Segmentation 計算CT影像標記全身器官位置,或找到癌症患處等。 ### 競爭激烈 根據不同使用者習慣調整為最適合 ### AI 醫療方向 - 學術性發表 - 應用(和臨床合作) ### AI 劑量智動分配 - 依據正常器官與腫瘤的相對位置 - 考慮放置治療機器限制 - 放射物理學等知識 > 物理治療師需耗時約一天的時間左右 - Dose Planning ### AI預測計畫:用抗式生成網路應用於劑量預測 三個頻道(CT+TUMOR NORAL+ORGANS)重疊在一起使用生成網路進行劑量的預測。 - 計量預測-劑量智動系統 - 計算誤差 - 人爲判斷跟機器判斷(有物理限制) ### AI計畫評估:預後分析 ## 我們執行 AI 專案經驗分享 ### 改善AI效能的方法 - 改模型參數 - 選不同模型 - 訓練測略 - 改善資料 - 如何加快訓練模型的速度 #### 多 GPU 經驗: + 1個GPU,每個epoch訓練時間 2 小時 02 分鐘 + 4個GPU,每個epoch訓練時間爲55分鐘 > 每一個GPU都要等待其他GPU的計算結果, > 可以每一個GPU計算一種MODEL ==4個 GPU 推薦把 Batch 參數拉大== #### 血管沒那麼簡單,怎麼辦? + 嘗試 1 使用mask RCNN來測試 + 嘗試 2 3D模型設計 + 嘗試 3 2.5D多渠道Mask-RCNN設計 + 嘗試 4 2D全景分割模型設計 ### 結論 + 臨床問題導向 + 乾淨大資料為王 + 多嘗試模型、細心照顧、佛系AI + 回歸臨床使用 ###### tags: `MOPCON 2019`

    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