Composite Coding and Structured Representation of JAMI Standard Dosage Instructions in Medication Information Models

>100 Views

November 16, 26

スライド概要

第46回医療情報学連合大会で口演した内容です。
日本医療情報学会標準用法マスターは食前食後などのタイミングと投与経路などの複数の用語を合成して16桁のコードとして整理しています。それぞれの用語を分割して用いることは推奨されておらず、16桁での運用が推奨されていますが、実際に16桁で運用するためにはHL7 V2やFHIR, openEHR側で対応を工夫せざるを得ません。それであれば、合成コードではなく正規化した用語で利用した方がいいのではないかという問題提起です。

profile-image

スライドで断りのないものはCC-BYライセンスで公開しています。自由に改変、再配布してもらって構いませんが、出典は明記してください。 1970年生まれ。マイコン少年として育ち、1995年に医師免許取得。以後、血液内科で修練すると同時にインターネット、情報システムに興味を持ち医療情報学の研究を始める。 医療分野のオープンソースソフトウェア、医療情報標準規格について研究、医療DX教育にも携わってきた。

シェア

またはPlayer版

埋め込む »CMSなどでJSが使えない場合

ダウンロード

関連スライド

各ページのテキスト
1.

J AMI DOS AGE T ERMINOL OGY / J CMI 20 2 6 Composite Coding and Structured Representation of JAMI Standard Dosage Instructions in Medication Information Models KOBAYASHI Shinji Gifu University One code. Defined components. 01 / 11

2.

DI SCLOSU RE Conflict of Interest Disclosure No conflicts of interest to disclose. In relation to this presentation. 02 / 11

3.

0 1 T HE TERMI NOLOGY One code, several defined components Rebamipide 100 mg tablets One tablet per dose, three times daily after breakfast, lunch, and dinner. 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 1 0 1 3 0 4 4 4 0 0 0 0 0 0 0 0 POSI TI ON 1 POSI TI ON 2 POSI TI ON 3 POSI TI ON 4 POSI TI ONS 6 –8 Usage category Usage detail Timing category Daily frequency Meal timing Oral medication By mouth Meal-related 3 per day Dinner · lunch · breakfast Each 4 in positions 6–8 specifies “after the meal” in this regimen. Medication identity, strength and dose per administration remain separate. [1] JAHIS Ver.3.0C, §7.17, Tables 7.17.1, 7.17.2 and 7.17.4 03 / 11

4.

0 2 T HE QU ESTI ON What should the JAMI dosage master support? Start with the receiving task—not the inherited code structure. Users Tasks Representations Prescribing systems Receiving systems Clinical users Display the instruction Populate medication data Interpret and validate Composite code Structured components Explicit relationship Can one terminology support both modes of use? HL7 V2, FHIR and openEHR are implementation contexts—not a ranking of standards. Conceptual workflow based on the author’s study question and supplied prescription example 04 / 11

5.

0 3 E STAB LIS HED EXCHAN GE HL7 V2: an established exchange use case Rebamipide 100 mg · 1 tablet per dose · three times daily after meals ENCODED SEGMENT EXAMPLE / SYNTHETIC, 7-DAY SUPPLY RXE||REB100^Rebamipide 100 mg^99DEMO|1||TAB^錠^MR9P |||||21|TAB^錠^MR9P||||||||3^TAB&錠&MR9P TQ1|1|1|1013044400000000 &内服・経口・1日3回朝昼夕食後&JAMISDP01|||7^D&日&ISO+ RXR|PO^口^HL70162 RXE / DOSE TQ1-3 / COMPOSITE CODE RXR-1 / ROUTE RXE-3 + RXE-5: 1 tablet Oral · 3 times daily PO: oral RXE-19: 3 tablets per day After breakfast, lunch and dinner Also present in the JAMI code REB100 / 99DEMO: fictitious local drug code. 7 days / 21 tablets assumed. Display wraps within RXE and TQ1. The oral route is represented in both TQ1-3 and RXR-1. [1] JAHIS Ver.3.0C, §§7.15–7.17. Author-constructed segment excerpt; not a complete HL7 message. 05 / 11

6.

0 4 S TRUCT URED REPR ESENT ATI ON JP Core: the code and its components coexist MedicationRequest → dosageInstruction (Dosage) Two distinct issues SEL ECT ED E LEMENT S IN THI S E XAMPLE timing.code 1013044400000000 Usage + route + frequency + timing timing.repeat frequency 3 · period 1 d when PCM · PCD · PCV TEMPORAL OVERLAP Frequency and timing can appear in both code and repeat. BROADER SEMANTIC SCOPE route PO · oral doseAndRate.doseQuantity 1 tablet Usage category and route extend beyond a timing schedule. Coexistence requires explicit meaning and consistency rules. [2] FHIR R4: Timing and Dosage. [3] JP Core v1.2.0: MedicationDosage. 06 / 11

7.

0 5 P ROFIL E DESI GN JP Core already addresses JAMI components Selected coding slices within Dosage.method method.coding unitDigit1 JAMI basic usage · 1-digit code unitDigit2 Reuse established terminologies JP Core has a terminology WG. Established standards were preferred where available. JAMI detailed usage · 2-digit code Profile slicing is shown here—not a custom extension. Support component-level use without losing meaning or compatibility. [3] JP Core v1.2.0: method.coding slices. Redrawn from the author’s profile screenshot. 07 / 11

8.

0 6 C ONS IST ENCY What happens when the representations disagree? HYPOTHETICAL INCONSISTENCY timing.code timing.repeat 1013044400000000 frequency 2 · period 1 d ≠ 3 times / day 2 times / day Which representation should the receiver trust? 01 Generate coherently 02 Check consistency Hypothetical example, not an observed incident. [2] FHIR R4 Timing.code; proposed operational response. 03 Resolve discrepancies 08 / 11

9.

0 7 A NOT HER MODE L openEHR: the same requirement in another model Timing–daily • selected elements Can the relevant JAMI meanings be used here? Timing–daily Frequency Interval Specific event Event name Time offset Explicit definitions Context and dependencies Agreed mapping rules Another implementation context—not a validated JAMI binding. [4] Selected labels redrawn from the Timing–daily diagram in the supplied deck. 09 / 11

10.

0 8 P ROPOSAL Maintain supported uses—not only a code list JAMI terminology maintainers JP Core working groups Component meanings Context and dependencies Supported uses and compatibility Terminology WG + medication WG Element semantics and bindings Implementation requirements Joint review Shared use cases and component-level guidance Mappings · validation · discrepancy handling Build on existing terminology work; connect implementation needs to maintenance. Proposed joint requirements, based on the author’s implementation experience and study question. 10 / 11

11.

CONCL USIONS Preserve the code. Enable its components. 01 Preserve established exchange. 02 Support components with context. 03 Coordinate with terminology maintainers. Which use cases require the complete code? The question is not whether the 16-digit code should exist. 11 / 11