MISAC dev
  • NEW!
    NEW!  Connect Ideas Across Notes
    Save time and share insights. With Paragraph Citation, you can quote others’ work with source info built in. If someone cites your note, you’ll see a card showing where it’s used—bringing notes closer together.
    Got it
        • 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 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
      • 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 Help
    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
    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 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
    # Chest X ray and CT Structured Report:SR - 最終目的是產生肺癌標準化病歷範例 -- 包含結構化、標準化健康醫療紀錄、放射影像、數位病理、基因檢測資料 -- 可應用於臨床、研究、學習、公衛管理 - **初期針對 Chest X ray and CT 發展FHIR 結構化報告範例** - 以利延伸應用 -- 發表論文及公告文件 -- 基於此範例,做教育推廣 -- 合提計畫,探討其延伸應用 ## 作法 - 臨床專家(肺癌診治專家)與醫資標準專家合作,確立標準規和及應用案例 - 撰寫 Paper、範例文件、及教案 ## 檢查情境 - 基於[標準化醫學影像檢查流程](https://hackmd.io/RrrVG92wTUaRI1BSwUqTfw?view),再細分篩檢、定期追蹤、診治過程取像、其他等不同情境。**不同情境,影像檢視重點及報告內容應不相同?**。 -- 例如診治過程取像:基於病人狀況,門診給定胸部影像檢查處方。 -- 又如胸腔科住院病人造影,了解病人肺部現況 -- 又如[手術後追蹤](https://www.facebook.com/photo/?fbid=10227262848212754&set=a.1959532623751) 註: 不同情境,診斷重點可能不相同(不同的結構化報告?),診斷前需參考的資訊可能不同(如病人主訴、先前影像、其他檢驗檢查結果),建議由專科醫師提供更明確的需求 ## 現行 FHIR SR 規範 - 已有一些初步內容,但尚須與各專科合作,訂立細部規範,並在逐步推行。如下個國際標準組織之規範: ### [FHIR breast SR](https://build.fhir.org/ig/HL7/fhir-breast-radiology-ig/index.html) - [Mammo.SR finding SR](https://build.fhir.org/ig/HL7/fhir-breast-radiology-ig/StructureDefinition-MGFinding.html) 有最完善的結果,需進一步基於應用情境,實作、試用及評估規範是否恰當 ### [US Core Data for Interoperability USCDI](https://build.fhir.org/ig/HL7/US-Core/uscdi.html) - USCDI 包含初步的 FHIR image SR,如下截圖: ![](https://i.imgur.com/fpM1LOn.png) - 上圖連結包含USCDI image diagnosticreport 及 USCDI FHIR observation findings -- [USCDI image diagnosticreport](https://build.fhir.org/ig/HL7/US-Core/StructureDefinition-us-core-diagnosticreport-note.html)、[example](https://build.fhir.org/ig/HL7/US-Core/StructureDefinition-us-core-diagnosticreport-note-examples.html) -- [USCDI FHIR observation findings](https://build.fhir.org/ig/HL7/US-Core/StructureDefinition-us-core-observation-clinical-result.html),其中包含影像檢查發現及臆斷範例[FHIR Observation image finding](https://build.fhir.org/ig/HL7/US-Core/StructureDefinition-us-core-observation-clinical-result-examples.html) : 檢視下列連結範例 ![](https://i.imgur.com/EQonryt.png) ### [MISAC](https://hackmd.io/Q1sPmblxTBK59OVeitzyzg?view) - MISAC FHIR image SR Working Group chairman 所提 FHIR image SR 說明 : [FHIR Radiology-Structured Report](https://hackmd.io/@victoriatjia/fhir-sr) - [FHIR Radiology-Image Finding form and Diagnostic Report Format](https://hackmd.io/@victoriatjia/fhir-module-radiology) : 近期將進行 FHIR SR 表單入門教育訓練 - [Draft FHIR SR for BMD、Chest X ray、Liver](https://hackmd.io/@victoriatjia/fhir-module-radiology#%F0%9F%92%A1-What%E2%80%99s-Next) ## [TCU Chest X ray 肺部病變表單](https://drive.google.com/drive/folders/1FF5ifoPPRbVowT0gI55DtXKVd4IGgMQh?usp=share_link) - 選擇肺部病變種類,再填病變細部描述(如下) ![](https://i.imgur.com/D3SVxGf.png) ![](https://i.imgur.com/fEMpYyo.png) 注: 需與臨床專家進一步討論 1. 配合的臨床作業情境(健檢、胸腔科門診...)、相關臨床資料(病人主訴、過去病史、聽診、檢驗) 2. 基於案例,進一步討論表單輸入內容是否合適 3. 搭配影像標記,明確標記病變部位 4. 彙整匿名案例,以 [FHIR encounters](https://hackmd.io/pN_e8t7_TPyIzQZc1g0FUQ?both#Encounter-initiated-smart-services)(包含篩檢、看診、影像檢查、回診看到告之 encounter) 連結就醫過程資訊 ### [DICOM Chest CDA SR](https://dicom.nema.org/medical/dicom/current/output/chtml/part16/sect_ChestCADSRIODTemplates.html) - DICOM SR 優缺點 -- 優: 領域專家多年經驗訂立。 DICOM SR 可存放在 PACS server -- 缺: DICOM SR 規範一般資訊人員較難了解及上手開發,需學習不少 DICOM 知能,方可發展系統產生、處理、及呈現 DICOM SR 資料 註: 一般 IT 人員可快速上手了解 FHIR JSON data 及其 API,醫學領域專家花大約一天的教育訓練,也可了解所需之 FHIR JSON reource (如上範例),並能在其專業領域延應用。 可再準備延伸應用說明文件 ### Others - [連老師 FHIR影像報告: 通用病理 + 肺癌病理報告](https://mitw.dicom.org.tw/IG/NSCLC/) - RSNA lung -- [Rad Chest 2 Views](https://radreport.org/home/50271/2017-11-14%2017:22:09)、 [CT Onco Lung Mass](https://radreport.org/home/16/2009-12-01%2000:00:00) ## Unmet needs and proposed solution in constructing interactive image learning systems using FHIR standard. - Introduction -- Image based training for radiology diagnosis -- Chest X ray and CT diagnosis use case --- 說明胸腔科影像檢查應用情境、及取得相關臨床資料,以利診斷(含 accessment 及處置建議) -- 說明現行影像教案產生及及管理不足之處: Unmet needs of clinical data accumlication for elearning integration - Purpose -- 導入 FHIR 國際標準,以利: -- 1. 將影像發現及報告的描述資料(code and termolgy 標準化) -- 2. 利於彙整其他臨床資料 -- 3. 可將標準化教案存放於 FHIR 內容(文件)管理系統(Learning Content Management System:LCMS ),以利與各醫院及學校的入口網站及數位學習系統(Learning Content Management System:LCMS )整合應用 -- Method --1. 以 Chest X ray and CT 檢查為範例,FHIR SR 產生流程,及包含的內容 --1.1 醫學影像檢查流程 (愛佳的圖 示意圖 及包含的 FHIR resources 圖) --1.2 包含的 FHIR resources 概述: 檢查流程的 resources ,以及影像報告包含的 resources --1.3 說明 Chest X ray or CT 報告病歷(FHIR document) 包含內容及其呈現結果 --1.4 說明其他病歷,如門診紀錄、檢驗(含基因、及病理)報告,也可產生 FHIR document --2. 影像教案產生 ---2.1 匿名化 ---2.2 加入測驗 ---2.3 索引及註冊 registrating documentReference in portal -3 Result --3.1 展示案例庫及其查詢介面(在 portal) --3.2 與數位學習平台整合應用 --3.3 與各單位數位學習環境整合方案及其授權 -4 Discussion: - 最終目的是產生肺癌標準化病歷範例 -- 包含結構化、標準化健康醫療紀錄、放射影像、數位病理、基因檢測資料 -- 可應用於臨床、研究、學習、公衛管理 - **初期針對 Chest X ray and CT 發展FHIR 結構化報告範例** - 以利延伸應用 -- 發表論文及公告文件 -- 基於此範例,做教育推廣

    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 Google 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