Token导航 LogoToken导航

Agent Skill · 前端设计

hl7-pam-parser(hl7 pam 解析器)

用于辅助前端页面、组件、样式和交互逻辑的开发与维护。它适合让 Agent 生成或审查 React、Next.js、Vue、Tailwind、CSS 等相关代码,整理组件结构,或定位布局和性能问题。使用时需要结合项目现有设计系统、路由和构建方式,避免只生成孤立片段;涉及页面改动时,应配合本地预览和构建检查确认视觉效果。

hl7-pam-parser 是前端设计类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证为 MIT,第三方扫描已通过,按安装量在前端设计类的 10,216 个 Skill 里排第 2,073。

总安装 2,940周安装 125GitHub Stars 3下载 1,030核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:hl7-pam-parser(hl7 pam 解析器)
来源仓库:https://github.com/dedalus-erp-pas/foundation-skills
仓库路径:skills/hl7-pam-parser
安装命令:
npx skills add https://github.com/dedalus-erp-pas/foundation-skills --skill hl7-pam-parser
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。不同来源提供的安装方式可能略有差异;本站展示可直接复制的安装命令,安装前请核对来源页面。

skills.shnpx skills
npx skills add https://github.com/dedalus-erp-pas/foundation-skills --skill hl7-pam-parser

这个 Skill 是做什么的

前端设计类 Skill 关注页面结构、视觉规范和组件写法,输出通常是可运行的界面代码。

hl7-pam-parser 用于辅助前端页面、组件、样式和交互逻辑的开发与维护。适合生成或审查 React、Next.js、Vue、Tailwind、CSS 等相关代码,整理组件结构或定位布局问题。使用时需结合项目现有设计系统、路由和构建方式,避免生成孤立片段;涉及页面改动应配合本地预览检查。

通过 npx skills add 命令从指定仓库安装,需结合原始 README 核验具体用法。适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

来源仓库内路径:skills/hl7-pam-parser

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/dedalus-erp-pas/foundation-skills --skill hl7-…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

hl7-pam-parser 怎么安装?

在终端执行 npx skills add https://github.com/dedalus-erp-pas/foundation-skills --skill hl7-pam-parser。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

hl7-pam-parser 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

hl7-pam-parser 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

hl7-pam-parser 是免费的吗?

来源标注的许可证是 MIT。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

hl7-pam-parser 用的人多吗?

公开数据是累计安装 2,940 次,近一周安装 125 次,下载 1,030 次,GitHub 3 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

hl7-pam-parser 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 3 个目录同时收录,说明这个 Skill 流传比较广。
  • 许可证明确为 MIT,商用和分发边界好判断。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理前端设计类任务、又不想每次都手写提示词的人。
  • 需要许可证清楚、并且有第三方扫描结果的团队项目。

不太适合

  • 需要厂商级技术支持和 SLA 的生产系统。

前端设计类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
frontend-design

前端设计 · Codex、Claude

8,823,360126,072只读MIT通过
vercel-composition-patterns

Vercel 组合模式 · Codex、Claude

3,858,81625,893需要联网MIT通过
vercel-react-native-skills

Vercel React native skills 前端 · Codex、Claude

2,468,66425,878只读MIT通过
adapt

adapt 搜索 · Codex、Claude

2,027,04023,125操作浏览器未明确通过
bolder

bolder 分析 · Codex、Claude

2,004,28823,130只读未明确通过
hl7-pam-parser

hl7 pam 解析器 · 本页

2,9403只读MIT通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

HL7 IHE PAM Message Parser and Explainer

Overview

This skill parses and explains HL7 v2.5 IHE PAM (Patient Administration Management) messages - the standard healthcare interoperability format for patient administration events. The parser identifies message types, extracts segments and fields, validates structure according to IHE PAM 2.10 specifications, and provides human-readable explanations.

When to use this skill:

  • Parse and explain any HL7 ADT message (raw HL7 text)
  • Identify HL7 message type and event code (ADT^A01, ADT^A02, etc.)
  • Extract and label all segments and fields (MSH, EVN, PID, PV1, PV2)
  • Validate HL7 message structure and required fields
  • Understand IHE PAM business rules and field mappings
  • Debug HL7 message issues or data quality problems
  • Document HL7 message examples with explanations

HL7 v2.5 Message Format

HL7 messages use specific delimiters:

Field delimiter:        |  (pipe)
Component delimiter:    ^  (caret)
Repetition delimiter:   ~  (tilde)
Escape character:       \  (backslash)
Subcomponent delimiter: &  (ampersand)

Basic Structure:

MSH|^~\&|SendingApp|SendingFacility|ReceivingApp|ReceivingFacility|Timestamp||MessageType|MessageControlId|ProcessingId|VersionId
EVN|EventTypeCode|RecordedDateTime|...
PID|SetId||PatientId||PatientName||BirthDate|Sex|...
PV1|SetId|PatientClass|AssignedPatientLocation|...

Segment Terminators: Each segment ends with carriage return (\r) or newline (\n)

IHE PAM Message Types

ADT Messages (Admit, Discharge, Transfer)

ADT^A01 - Admit/Visit Notification

Purpose: Patient admission to inpatient care or registration

Required Segments:

  • MSH (Message Header)
  • EVN (Event Type)
  • PID (Patient Identification)
  • PV1 (Patient Visit)

Example:

MSH|^~\&|HEXAFLUX|CHU_PARIS|TARGET|DEST|20260122140000||ADT^A01^ADT_A01|MSG001|P|2.5
EVN|A01|20260122140000|||USER001
PID|1||PAT12345^^^CHU_PARIS^PI||DUPONT^JEAN^^M.||19750315|M|||15 RUE DE LA PAIX^^PARIS^^75001^FRA||(33)612345678
PV1|1|I|CHU_PARIS^CARDIO^LIT_001^CHU_PARIS||||PR_MARTIN^MARTIN^SOPHIE|||CARDIO||||||||||VIS20260122001|||||||||||||||||||||||||20260122140000

Explanation:

  • Event: A01 (Patient Admission)
  • Patient: DUPONT JEAN (M.), born 15/03/1975
  • Patient ID: PAT12345
  • Visit: VIS20260122001
  • Location: CHU_PARIS, Cardiology, Bed LIT_001
  • Admission: 22/01/2026 14:00:00
  • Patient Class: I (Inpatient)
  • Attending: Dr. MARTIN SOPHIE
ADT^A02 - Transfer a Patient

Purpose: Patient transfer between units, rooms, or services

Required Segments:

  • MSH, EVN, PID, PV1
  • PV2 (optional but recommended for prior location)

Example:

MSH|^~\&|HEXAFLUX|CHU_PARIS|TARGET|DEST|20260123090000||ADT^A02^ADT_A02|MSG002|P|2.5
EVN|A02|20260123090000|||USER002
PID|1||PAT12345^^^CHU_PARIS^PI||DUPONT^JEAN^^M.||19750315|M
PV1|1|I|CHU_PARIS^NEURO^LIT_102^CHU_PARIS||||PR_DURAND^DURAND^PAUL|||NEURO||||||||||VIS20260122001
PV2||||||||||||||||||||||CHU_PARIS^CARDIO^LIT_001^CHU_PARIS

Explanation:

  • Event: A02 (Patient Transfer)
  • Patient: PAT12345 (DUPONT JEAN)
  • From: Cardiology, Bed LIT_001 (PV2-1: prior location)
  • To: Neurology, Bed LIT_102 (PV1-3: assigned location)
  • Transfer Time: 23/01/2026 09:00:00
ADT^A03 - Discharge a Patient

Purpose: Patient discharge from hospital

Required Segments:

  • MSH, EVN, PID, PV1

Example:

MSH|^~\&|HEXAFLUX|CHU_PARIS|TARGET|DEST|20260125180000||ADT^A03^ADT_A03|MSG003|P|2.5
EVN|A03|20260125180000|||USER003
PID|1||PAT12345^^^CHU_PARIS^PI||DUPONT^JEAN^^M.||19750315|M
PV1|1|I|CHU_PARIS^CARDIO^LIT_001^CHU_PARIS||||PR_MARTIN^MARTIN^SOPHIE|||CARDIO||||||||||VIS20260122001|||||||||||||||||||||||||||20260125180000|||||HOME

Explanation:

  • Event: A03 (Patient Discharge)
  • Patient: PAT12345 (DUPONT JEAN)
  • Discharge Time: 25/01/2026 18:00:00 (PV1-45)
  • Discharge Disposition: HOME (PV1-36)
  • Visit: VIS20260122001
ADT^A04 - Register a Patient

Purpose: Pre-admission or outpatient registration

Required Segments:

  • MSH, EVN, PID, PV1
ADT^A05 - Pre-admit a Patient

Purpose: Pre-admission notification

ADT^A06 - Change Outpatient to Inpatient

Purpose: Convert outpatient visit to inpatient admission

ADT^A07 - Change Inpatient to Outpatient

Purpose: Convert inpatient admission to outpatient visit

ADT^A08 - Update Patient Information

Purpose: Update patient demographics

Example:

MSH|^~\&|HEXAFLUX|CHU_PARIS|TARGET|DEST|20260122150000||ADT^A08^ADT_A08|MSG004|P|2.5
EVN|A08|20260122150000|||USER001
PID|1||PAT12345^^^CHU_PARIS^PI||DUPONT^JEAN^^M.||19750315|M|||15 RUE DE LA PAIX^^PARIS^^75001^FRA||(33)612345678|||||||1234567890123||FRA
PV1|1|O||||||||||||||||||||VIS20260122001

Explanation:

  • Event: A08 (Update Patient Information)
  • Patient: PAT12345 demographics updated
  • Updated Fields: Address, phone, national identifier (NIR)
ADT^A11 - Cancel Admit

Purpose: Cancel a previous admission

ADT^A12 - Cancel Transfer

Purpose: Cancel a previous transfer

ADT^A13 - Cancel Discharge

Purpose: Cancel a previous discharge

Segment Definitions

MSH - Message Header (Required)

Purpose: Message metadata and routing information

Field Structure:

MSH|^~\&|SendingApp|SendingFacility|ReceivingApp|ReceivingFacility|Timestamp||MessageType^EventCode^MessageStructure|MessageControlId|ProcessingId|VersionId

Key Fields:

  • MSH-3: Sending Application
  • MSH-4: Sending Facility
  • MSH-5: Receiving Application
  • MSH-6: Receiving Facility
  • MSH-7: Date/Time of Message (YYYYMMDDHHmmss)
  • MSH-9: Message Type (ADT^A01^ADT_A01)
  • MSH-10: Message Control ID (unique identifier)
  • MSH-11: Processing ID (P=Production, T=Training, D=Debugging)
  • MSH-12: Version ID (2.5)

EVN - Event Type (Required)

Purpose: Event-specific information

Field Structure:

EVN|EventTypeCode|RecordedDateTime|EventDateTime|EventReasonCode|OperatorId

Key Fields:

  • EVN-1: Event Type Code (A01, A02, A03, etc.)
  • EVN-2: Recorded Date/Time (when event was recorded)
  • EVN-3: Event Occurred Date/Time (when event actually occurred)
  • EVN-5: Operator ID (user who triggered the event)

PID - Patient Identification (Required)

Purpose: Patient demographic information

Field Structure (30+ fields):

PID|SetId||PatientId^^^AssigningAuthority^IdType~AltId||LastName^FirstName^MiddleName^Suffix^Prefix||BirthDate|Sex|PatientAlias|Race|PatientAddress||PhoneHome|PhoneBusiness|PrimaryLanguage|MaritalStatus|Religion|PatientAccountNumber|SSN|DriverLicense|MotherIdentifier|EthnicGroup|BirthPlace|MultipleBirth|BirthOrder|Citizenship|VeteranStatus|Nationality|DeathDateTime|DeathIndicator

Key Fields:

  • PID-1: Set ID
  • PID-3: Patient Identifier List (PatientId^^^Facility^PI)
  • PID-5: Patient Name (LastName^FirstName^MiddleName^Suffix^Prefix)
  • PID-7: Date of Birth (YYYYMMDD)
  • PID-8: Sex (M/F/O/U)
  • PID-11: Patient Address (Street^^City^^PostalCode^Country)
  • PID-13: Phone Number - Home
  • PID-14: Phone Number - Business
  • PID-22: Ethnic Group
  • PID-29: Death Date and Time
  • PID-30: Death Indicator (Y/N)

PV1 - Patient Visit (Required)

Purpose: Visit/encounter information

Field Structure (52 fields):

PV1|SetId|PatientClass|AssignedLocation^Room^Bed^Facility|AdmissionType|PreadmitNumber|PriorLocation|AttendingDoctor^LastName^FirstName|ReferringDoctor|ConsultingDoctor|HospitalService|TemporaryLocation|PreadmitTestIndicator|ReadmissionIndicator|AdmitSource|AmbulatoryStatus|VIPIndicator|AdmittingDoctor|PatientType|VisitNumber|FinancialClass

Key Fields:

  • PV1-1: Set ID
  • PV1-2: Patient Class (I=Inpatient, O=Outpatient, E=Emergency, R=Recurring)
  • PV1-3: Assigned Patient Location (Facility^Service^Room^Bed)
  • PV1-4: Admission Type (E=Emergency, R=Routine, etc.)
  • PV1-6: Prior Patient Location (for transfers)
  • PV1-7: Attending Doctor (DoctorId^LastName^FirstName)
  • PV1-10: Hospital Service
  • PV1-19: Visit Number (unique visit identifier)
  • PV1-36: Discharge Disposition (HOME, SNF, EXP, etc.)
  • PV1-44: Admit Date/Time
  • PV1-45: Discharge Date/Time

PV2 - Patient Visit - Additional Info (Optional)

Purpose: Extended visit information

Key Fields:

  • PV2-1: Prior Pending Location (for transfers)
  • PV2-3: Admit Reason
  • PV2-8: Expected Discharge Date
  • PV2-9: Expected Discharge Disposition
  • PV2-47: Expected LOA Return Date/Time

IHE PAM Mandatory Fields

Required for All ADT Messages

  • MSH-3: Sending Application
  • MSH-4: Sending Facility
  • MSH-7: Date/Time of Message
  • MSH-9: Message Type
  • MSH-10: Message Control ID
  • MSH-12: Version ID (2.5)
  • EVN-1: Event Type Code
  • EVN-2: Recorded Date/Time
  • PID-3: Patient Identifier
  • PID-5: Patient Name
  • PID-7: Date of Birth
  • PID-8: Sex

Required for Admission/Transfer Messages (A01, A02)

  • PV1-2: Patient Class
  • PV1-3: Assigned Patient Location
  • PV1-19: Visit Number
  • PV1-44: Admit Date/Time

Required for Discharge Messages (A03)

  • PV1-36: Discharge Disposition
  • PV1-45: Discharge Date/Time

Parsing Logic

When asked to parse an HL7 IHE PAM message:

  1. Split by segment terminator: segments = message.split('\r') or split('\n')
  2. Parse MSH segment (always first):

- Extract delimiters from MSH-2: ^~\& - Field delimiter: | - Component delimiter: ^ - Repetition delimiter: ~ - Escape character: \ - Subcomponent delimiter: &

  1. Identify message type: Check MSH-9

- ADT^A01 = Admission - ADT^A02 = Transfer - ADT^A03 = Discharge - etc.

  1. Parse each segment:

- Split by field delimiter | - Parse components with ^ - Parse repetitions with ~ - Parse subcomponents with &

  1. Extract key fields:

- Patient ID (PID-3) - Patient name (PID-5) - Birth date (PID-7) - Visit number (PV1-19) - Location (PV1-3) - Dates (PV1-44, PV1-45)

  1. Validate structure:

- Check required segments present - Check required fields populated - Validate date formats (YYYYMMDD, YYYYMMDDHHmmss) - Validate code values (patient class, sex, etc.)

  1. Generate explanation:

- Identify message purpose - Explain event type - List key patient information - Describe visit/encounter details - Provide clinical context

Example Output Format

When parsing a message, provide:

### HL7 IHE PAM Message Analysis

**Raw Message**:

[original HL7 message with visible delimiters]

**Message Identification**:
- Message Type: ADT^A01
- Event Code: A01 (Admit/Visit Notification)
- Message Control ID: [MSH-10]
- Timestamp: [formatted MSH-7]
- Version: 2.5

**MSH - Message Header**:
- Sending Application: [MSH-3]
- Sending Facility: [MSH-4]
- Receiving Application: [MSH-5]
- Receiving Facility: [MSH-6]
- Processing ID: [MSH-11] (Production/Test)

**EVN - Event Type**:
- Event Code: [EVN-1]
- Recorded DateTime: [formatted EVN-2]
- Event Occurred: [formatted EVN-3]
- Operator: [EVN-5]

**PID - Patient Identification**:
- Patient ID: [PID-3]
- Patient Name: [formatted PID-5]
- Date of Birth: [formatted PID-7]
- Sex: [PID-8]
- Address: [formatted PID-11]
- Phone: [PID-13]
- [other relevant fields]

**PV1 - Patient Visit**:
- Patient Class: [PV1-2] ([description])
- Assigned Location: [formatted PV1-3]
- Attending Doctor: [formatted PV1-7]
- Hospital Service: [PV1-10]
- Visit Number: [PV1-19]
- Admit DateTime: [formatted PV1-44]
- [other relevant fields based on message type]

**PV2 - Additional Visit Info** (if present):
- Prior Location: [PV2-1]
- [other relevant fields]

**Business Context**:
[Explain what this message represents, the workflow event, and clinical significance]

**IHE PAM Compliance**:
- Required segments: [✓ or ✗ for MSH, EVN, PID, PV1]
- Required fields: [list of mandatory field validation results]
- Field formats: [✓ or ✗ for dates, codes, etc.]

Common ADT Event Codes

CodeEvent NamePurpose
A01Admit/Visit NotificationPatient admission to inpatient care
A02Transfer a PatientTransfer between units/rooms
A03Discharge a PatientPatient discharge from hospital
A04Register a PatientPre-admission or outpatient registration
A05Pre-admit a PatientNotification of planned admission
A06Change Outpatient to InpatientStatus change
A07Change Inpatient to OutpatientStatus change
A08Update Patient InformationDemographics update
A09Patient Departing - TrackingPatient left facility temporarily
A10Patient Arriving - TrackingPatient returned to facility
A11Cancel AdmitCancel previous admission
A12Cancel TransferCancel previous transfer
A13Cancel DischargeCancel previous discharge
A21Patient Goes on Leave of AbsenceTemporary leave
A22Patient Returns from Leave of AbsenceReturn from leave
A28Add Person InformationAdd new person to database
A31Update Person InformationUpdate person demographics

Patient Class Codes

CodeDescription
IInpatient
OOutpatient
EEmergency
PPreadmit
RRecurring patient
BObstetrics
CCommercial Account
NNot Applicable
UUnknown

Discharge Disposition Codes

CodeDescription
HOMEHome or self care
SNFSkilled nursing facility
RHRehabilitation facility
EXPExpired (deceased)
HOSHospice
AADVICELeft against medical advice
OTHOther

Validation Rules

Message Structure

  • First segment MUST be MSH
  • MSH-1 MUST be |
  • MSH-2 MUST be ^~\& (encoding characters)
  • Segments MUST be separated by CR or LF
  • Fields MUST be separated by |

Required Segments by Message Type

  • A01, A04, A05: MSH, EVN, PID, PV1
  • A02: MSH, EVN, PID, PV1 (PV2 recommended for prior location)
  • A03: MSH, EVN, PID, PV1
  • A08: MSH, EVN, PID (PV1 optional)
  • A11, A12, A13: MSH, EVN, PID

Date/Time Formats

  • Date: YYYYMMDD
  • DateTime: YYYYMMDDHHmmss or YYYYMMDDHHmmss.SSSS
  • Time: HHmmss

Patient Identifier Format

  • PID-3: PatientId^^^AssigningAuthority^IdentifierType
  • Example: PAT12345^^^CHU_PARIS^PI

Name Format

  • PID-5: LastName^FirstName^MiddleName^Suffix^Prefix^Degree
  • Example: DUPONT^JEAN^^M.

Location Format

  • PV1-3: PointOfCare^Room^Bed^Facility^LocationStatus^PersonLocationType^Building
  • Example: CHU_PARIS^CARDIO^LIT_001^CHU_PARIS

Reference Documentation

IHE PAM Specification:

HL7 v2.5 Standard:

Related Tools:

Quick Reference

Delimiters

|  Field delimiter
^  Component delimiter
~  Repetition delimiter
\  Escape character
&  Subcomponent delimiter

Common Fields

MSH-9  : Message Type (ADT^A01^ADT_A01)
MSH-10 : Message Control ID
EVN-1  : Event Type Code (A01, A02, etc.)
EVN-2  : Recorded DateTime
PID-3  : Patient ID
PID-5  : Patient Name
PID-7  : Birth Date
PID-8  : Sex
PV1-2  : Patient Class (I/O/E)
PV1-3  : Assigned Location
PV1-19 : Visit Number
PV1-44 : Admit DateTime
PV1-45 : Discharge DateTime

平台分布

Claude Code

28.55%
按下载量换算294

OpenCode

23.92%
按下载量换算246

Antigravity

17.28%
按下载量换算178

Gemini CLI

11.42%
按下载量换算118

windsurf

8.26%
按下载量换算85

Codex

3.56%
按下载量换算37

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。

继续浏览同类 Skills