Tsung-Jung Tsai (TJ_Tsai)
    • 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 No publishing access yet

      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.

      Your account was recently created. Publishing will be available soon, allowing you to share notes on your public page and in search results.

      Your team account was recently created. Publishing will be available soon, allowing you to share notes on your public page and in search results.

      Explore these features while you wait
      Complete general settings
      Bookmark and like published notes
      Write a few more notes
      Complete general settings
      Write a few more notes
      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 New
    • Engagement control
    • Make a copy
    • 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 Note Insights Versions and GitHub Sync Sharing URL Create Help
Create Create new note Create a note from template
Menu
Options
Engagement control Make a copy 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 No publishing access yet

    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.

    Your account was recently created. Publishing will be available soon, allowing you to share notes on your public page and in search results.

    Your team account was recently created. Publishing will be available soon, allowing you to share notes on your public page and in search results.

    Explore these features while you wait
    Complete general settings
    Bookmark and like published notes
    Write a few more notes
    Complete general settings
    Write a few more notes
    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
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    [AI] 落地應用 === ###### tags: `AI Tools` ###### tags: `AI`, `tools`, `落地應用` <br> [TOC] <br> :::info :bulb: - [[AI] 落地應用](https://hackmd.io/n1ZCa7K5THW7eTPXyjTKpw) - [[AI] 工具再創新](https://hackmd.io/Zx3U8i_qRQSCz--vemuFfw) ::: <br> ## News ### 2025/11/01 - [【從臨床痛點出發,自己的痛點靠AI自己解!】中山附醫不只要推動醫護全員AI,還要發展區域AI醫療生態系 | iThome](https://www.ithome.com.tw/news/171991) - ### gpt-5 (2025/11/06) ### 核心重點: * **核心**:中山附醫自建「醫點家」GenAI 平臺,<1 年做出 600+ 小幫手,60+ 上架共用。 * **成效**:入院護理紀錄 103.8 分→<6 分;護理摘要 44.8 分→約 5 分;藥師 SOAP 20 分→<3 分;病房服務 5→8–9 次/日。 * **設計**:外掛式並行 HIS、臨床資料流程標準化、善用公有雲;以「1% 計畫」由下而上小規模導入。 * **方向**:打造 AI 小幫手「App Store」,推進跨院擴散與區域級醫療生態系。 ### 報導整理 * **中山附醫自建「醫點家」GenAI 臨床平臺** 內部上線未滿一年,員工自行開發 **600+ 個 AI 小幫手**,其中 **60+** 已上架全院共用商城。從第一線護理到行政皆有應用。 * **效率成效(具體數字)** 入院護理紀錄:**103.8 分 → <6 分**;護理摘要:**44.8 分 → 約 5 分多**。 藥師 SOAP 報告:**20 分 → <3 分**;藥師病房服務次數:**5 次/日 → 8–9 次/日**。 * **平台設計三原則** 1. **外掛式**與 HIS 並行、避免重構; 2. **臨床資料處理流程標準化**、可重複執行; 3. **善用公有雲服務**以加速開發並兼顧隱私與資安。 * **四種運用模式** 自建小幫手/直接使用/**商城共享**(版控與授權)/**HIS 整合**(結果經人審可回寫 HIS)。支援多模態資料,任務流程模組化、可封裝與複製。 * **隱私與資料治理** 採**最小資料原則**;於 HIS 端先**去識別化**後才送公雲推論,回院再以專屬識別碼對應病人,降低外洩風險。並建立上架審核、使用監控與錯誤標記回饋機制。 * **架構與延伸** 走向雙層 **MedAssist Hub** 架構;平台被視為「**AI 工廠/AI 鑄造廠**」。成熟小幫手可做成 **SMART on FHIR** App(例:大腸鏡清腸準備小幫手,掃 QR 即用)。 * **推動路線圖** 2023/07 聚焦臨床痛點 → 2024/02 參與 GenAI Stars、確立策略 → 2024/10 內部上線 → 以「**1% 計畫**」在代表性場景小規模導入 → **2025/3–4 起推進跨院擴散**。 * **願景** 打造 **AI 小幫手的「App Store」**,串聯中小型醫院與診所,邁向**區域級 AI 醫療生態系**。 * **實際應用範例** 護理紀錄、急診高風險分流、影像報告病摘、超音波報告生成、藥事照護與 OSCE 模擬、會議紀錄摘要與比較、Transfer Note 等。 <br> --- ### 2025/10/23 - [結合資料中臺及Gemini,iCHEF年底推餐飲管理AI助手「春嬌」 | iThom](https://www.ithome.com.tw/news/171794) - ### gpt-5 (2025/10/21) 1. **事件與目標** * iCHEF 宣布「AI 戰略」,近期釋出 5 項 AI 模組; * 年底將推出餐飲管理 AI 助手「春嬌」,用以加速餐飲業 AI 化。 2. **覆蓋範圍與升級方式** * 逾 1 萬家餐廳可在不更換系統/不添購硬體下直接升級。 3. **五大 AI 模組(已上線)** * **點餐推薦**:依近 45 天營運數據推薦熱銷/組合。 * **智慧菜單管家**:一句話批次改價、調整套餐子選項,簡化維運。 * **多語系菜單**:自動偵測並翻譯多國語言。 * **AI 客服**:提供 24 小時 iCHEF 客服支援。 * **分析銷售**:下載門店營運診斷(營收、客單、來客等)。 4. **「春嬌」定位與技術架構(年底上線)** * 以「**資料中臺**」整合 POS/會員/庫存與 iCHEF 知識庫; * 管理者可用自然語言查詢營運、產出建議與預測(客流、銷售)。 * 與 RevtelTech、Google Cloud 合作,採 GCP + Gemini 2.5; * 用 RAG 與多 Agent(計算、報表等)降低幻覺。 5. **外部資料整合** * 可接天氣風險公司的「微氣候」資料(門市 3 公里範圍),提供備料與排班建議; * 亦規畫整合免費國際氣候資料。 6. **時程與計費** * **目標**:聖誕節前後推出; * **計費**:依雲端 LLM 用量,月費約在「千元以內」。 7. **產業觀點** * iCHEF 認為 2026 年將是臺灣餐飲業的「AI 元年」。 <br> --- - ### 2025/10/20 - [Google把世界裝進Gemini!AI與地圖融合開啟「智慧空間時代」](https://ai.ettoday.net/amp/amp_news.php7?news_id=3053482) - **Google 官方也列舉出幾種應用情境**: - 旅遊規劃:輸入想去的城市與景點,AI 會自動安排行程、估算交通時間,甚至顯示地圖。 - 在地推薦:根據所在位置與偏好,推薦合適的餐廳、商圈或租屋區域。 - 店家查詢:能直接回答「這家店週末幾點關」或「有沒有戶外座位」。 - 商業分析:企業可用於分析門市表現或配送路線規劃。 - 這些答案都不是「AI 想像出來的」,而是根據 Maps 的真實資料生成,並且會自動附上來源。 <br> --- ### 2025/09/19 - [高雄市如何用主權生成式AI升級城市智慧治理,靠AI辨識火災、繞境等108種情境,要讓市府應變決策快一步 | iThom](https://www.ithome.com.tw/news/171310) - ### gpt-5 (2025/09/25) ### 高雄「主權生成式 AI 燈塔計畫」重點 * **定位與目標** * 以「城市級主權 AI」強化智慧治理:用 AI 讀取街頭監視器、公交與垃圾車行車紀錄器(未來拓展到計程車)影像,早於 1999 通報就自動偵測情境並通報處置(火災、淹水、塞車等)。 * 聚焦「適地性」與「資料主權」:例如特別辨識台灣在地的廟會繞境,以管理噪音與交通影響。 * **能力指標** * 建置城市級 **VLM 推論平臺**:目前可辨識 **108 種情境**、設計 **609 個判斷指標**;輸出同時提供自然語言描述(便於人讀)與指標/分級(便於系統 API 對接)。 * **合作與建置模式** * 與 **鴻海、NVIDIA、Linker Vision、中華電信** 等採「聯合開發」:共同投資、權利義務共享;在高雄軟體園區建先進算力中心,並以 **NVIDIA GB200** 擴充算力。 * 設備與機房配置:主機與資料放在 **中華電信七賢機房(高雄)**,GPU 在 **中華電信臺南機房**,兩地以全光纖連接。 * 平臺分層:在 **PaaS 層**微調 NVIDIA 商模成「城市大腦」,再由各局處以 **SaaS 應用**串接(環保、交通、治安等既有系統需改版銜接)。 * **與數位孿生整合** * 以 **NVIDIA Omniverse** 打造高雄 **80 km²** 數位孿生;事件於孿生中同步呈現並推送至各局處系統,利於橫向協同。 * **實際/規劃情境** * 道路坑洞自動判讀與派工排序、廟會繞境偵測與交通/噪音管理、交通壅塞即時通報與市民推播。 * 與台電等單位合作:無人機巡檢影像由城市大腦判讀(如電塔鏽蝕)以安排檢修。 * 下一步:從「自動報告」邁向「自動控制」(如聯動號誌秒數、水利閘門),走向類 Agentic AI。 * **資料取得與模型訓練** * 針對罕見、極端案例(例如火災)以 **生成式資料**補足訓練與測試,提升在各種時段/天候下的辨識穩健度。 * **參與單位與生態** * 市府與 **中鋼、中油、港務公司、台電** 等公營/民間單位合作,並正與醫療機構、企業、大學洽談擴用。 > 來源:iThome〈高雄市如何用主權生成式AI升級城市智慧治理,靠AI辨識火災、繞境等108種情境,要讓市府應變決策快一步〉,發表日期 **2025-09-19**。 需要把這份重點改成簡報或流程圖版嗎?我可以直接幫你排成 1–2 張投影片(含圖示與架構示意)。 <br> {%hackmd vaaMgNRPS4KGJDSFG0ZE0w %}

    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
    Sign in via Facebook Sign in via X(Twitter) Sign in via GitHub Sign in via Dropbox Sign in with Wallet
    Wallet ( )
    Connect another wallet

    New to HackMD? Sign up

    By signing in, you agree to our terms of service.

    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