Back to Details

hexagone-swdoc

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Hexagone Web Services Documentation -- Navigation Skill

Hexagone Web服务文档 -- 导航技能

This skill gives you access to the Hexagone Web Services documentation ("Référence Appels Externes") published as GitLab Pages. Your role is to fetch and read the relevant pages when answering questions about Hexagone web services, not to rely on memorized knowledge.
本技能允许你访问发布在GitLab Pages上的Hexagone Web服务文档（即「外部调用参考」）。在回答关于Hexagone Web服务的问题时，你需要获取并读取相关页面内容，而不是依赖记忆中的知识。

What is Hexagone swdoc

什么是Hexagone swdoc

The Hexagone "Appels Externes" module (EW) exposes SOAP web services that allow external applications to invoke Hexagone Web business logic. The documentation is organized by service module (EWPT0001, EWPT0002, etc.), each grouping methods for a specific healthcare domain.
The documentation is published at:
https://erp-pas.gitlab-pages-erp-pas.dedalus.lan/hexagone/swdoc/
When to use this skill:
  • The user asks about a Hexagone web service, SOAP method, or EWPT service
  • The user needs to understand how to call a specific Hexagone API method
  • The user is integrating with Hexagone and needs the service contract (parameters, DTDs)
  • The user asks about XML DTD formats (CASE.HEXASERV, PATIENT_INFO.HEXASERV, etc.)
  • The user wants to know which methods are available for a given domain (patients, movements, emergencies, etc.)
  • The user is debugging an integration issue (error codes, statuts, configuration)
  • The user asks about Hexagone API error codes or error handling (RESULT.HEXACALLW)
  • Any question mentioning "Hexagone" combined with "web service", "API", "EWPT", "appels externes", "service web", or "WS"
Hexagone的「外部调用」模块（EW）对外暴露SOAP Web服务，允许外部应用调用Hexagone Web的业务逻辑。文档按照服务模块（EWPT0001、EWPT0002等）组织，每个模块聚合了特定医疗领域的相关方法。
文档发布地址为：
https://erp-pas.gitlab-pages-erp-pas.dedalus.lan/hexagone/swdoc/
适用场景：
  • 用户询问Hexagone Web服务、SOAP方法或EWPT服务相关问题
  • 用户需要了解如何调用特定的Hexagone API方法
  • 用户正在与Hexagone做集成，需要服务契约（参数、DTD）相关信息
  • 用户询问XML DTD格式（CASE.HEXASERV、PATIENT_INFO.HEXASERV等）相关问题
  • 用户想知道特定领域（患者、流转、急诊等）可用的方法有哪些
  • 用户正在排查集成问题（错误代码、状态、配置）
  • 用户询问Hexagone API错误代码或错误处理（RESULT.HEXACALLW）相关问题
  • 任何同时提及「Hexagone」与「web service」、「API」、「EWPT」、「appels externes」、「service web」或「WS」的问题

Service catalog

服务目录

The base URL for all pages is:
BASE_URL = https://erp-pas.gitlab-pages-erp-pas.dedalus.lan/hexagone/swdoc/
所有页面的基础URL为：
BASE_URL = https://erp-pas.gitlab-pages-erp-pas.dedalus.lan/hexagone/swdoc/

Complete service index

完整服务索引

ServiceDomainURL pathKey methods
IntroductionGeneral (auth, errors, data exchange)
00-introduction/
—
EWPT0001Gestion des patients
01-ewpt0001-gestion-des-patients/
READ_PATIENT, FIND_PATIENT, NEW_PATIENT, UPDATE_PATIENT, READ_COVERAGES, READ_KINS, READ_DOCTOR, READ_CHILDLINK, CREATE_CHILDLINK, UPDATE_CHILDLINK, DELETE_CHILDLINK, SET_NEWBORN_STATE, ASSIGN_PROT_PATIENT, UPDATE_PROT_PATIENT, READ_PROT_PATIENT, PATIENT_DEBT, READ_PATIENT_ADDR, NEW_PATIENT_ADDR, UPDATE_PATIENT_ADDR, DELETE_PATIENT_ADDR, LEGAL_REPRESENTATIVES, REQUEST_PATIENT_MERGE, REQUEST_PATIENT_MERGE2, READ_PATIENT_DEMAT
EWPT0002Gestion des urgences
02-ewpt0002-gestion-des-urgences/
READ_EMERGENCY, NEW_EMERGENCY, UPDATE_EMERGENCY, ENDOF_EMERGENCY, CANCEL_ENDOF_EMERGENCY, TO_OUTPATIENT, TO_INPATIENT, DELETE_EMERGENCY
EWPT0003Consultations externes
03-ewpt0003-gestion-des-consultations-externes/
NEW_OUTPATIENT, READ_OUTPATIENT, UPDATE_OUTPATIENT, DELETE_OUTPATIENT
EWPT0004Dossiers d'hospitalisation
04-ewpt0004-gestion-des-dossiers-d-hospitalisation/
READ_INPATIENT, NEW_INPATIENT, UPDATE_INPATIENT, DELETE_INPATIENT, CONFIRM_PREADMIT, READ_MOVEMENT, NEW_MOVEMENT, UPDATE_MOVEMENT, DELETE_MOVEMENT, CREATE_PENDING_VISIT_MVTS, MOVEMENT_AT, HOSP_BABY
EWPT0005Lecture des occupations
05-ewpt0005-lecture-des-occupations/
ACTIVE_EMERGENCIES, HOUSING_UF_OCC, UF_OCC, RESPCENTER_OCC, SERVICE_OCC, POLE_OCC, LOCALIZATION_OCC, AVAILABLE_BEDS, IN_HOSPITAL
EWPT0007Gestion des séjours
07-ewpt0007-gestion-des-sejours/
PATIENT_CASES, CASE_MVTS, MVT_HIST, HOSP_MODE_AT, NEW_HOSP_MODE, UPDATE_HOSP_MODE, DELETE_HOSP_MODE, READ_INFORMED_CONSENT, CHG_CASE_TYPE
EWPT0008Produits
08-ewpt0008-produits/
INIT_ENV, GET_GEST, GET_FAMILY, GET_UNIT, GET_TAXE, GET_ACCOUNT_NUMBER, GET_UFMAINSTORE, GET_CMP, GET_GROUPING, PRODUCT_VERIFICATION, GET_PRODUCT_NUMBER, PRODUCT_CREATION
EWPT0009Gestion du DMP
09-ewpt0009-gestion-du-dmp/
NEW_REJECTION, UPDATE_REJECTION, ACCESS_CODE, INFO_VITALE, READ_OTP, UPDATE_DMPINFO
EWPT0010Gestion des praticiens
10-ewpt0010-gestion-des-praticiens/
FIND_PRACT, NEW_PRACT, UPDATE_PRACT
EWPT0014Structures physiques
14-ewpt0014-gestion-des-structures/
CHACC_LOCALIZATION, FIND/READ/NEW/UPDATE/DELETE_BUILDING, FIND/READ/NEW/UPDATE/DELETE_FLOOR, FIND/READ/NEW/UPDATE/DELETE_BEDROOM, FIND/READ/NEW/UPDATE/DELETE_BED, FIND/READ/NEW/UPDATE/DELETE_LOCALIZATION
EWPT0012Intégration d'actes
12-ewpt0012-integration-d-actes/
INTEGR_CCAM
EWPT0013Re-génération Identités/mouvements
13-ewpt0013-re-generation-identites-mouvements/
REGEN_IDMVT
服务领域URL路径核心方法
介绍通用（认证、错误、数据交换）
00-introduction/
—
EWPT0001患者管理
01-ewpt0001-gestion-des-patients/
READ_PATIENT, FIND_PATIENT, NEW_PATIENT, UPDATE_PATIENT, READ_COVERAGES, READ_KINS, READ_DOCTOR, READ_CHILDLINK, CREATE_CHILDLINK, UPDATE_CHILDLINK, DELETE_CHILDLINK, SET_NEWBORN_STATE, ASSIGN_PROT_PATIENT, UPDATE_PROT_PATIENT, READ_PROT_PATIENT, PATIENT_DEBT, READ_PATIENT_ADDR, NEW_PATIENT_ADDR, UPDATE_PATIENT_ADDR, DELETE_PATIENT_ADDR, LEGAL_REPRESENTATIVES, REQUEST_PATIENT_MERGE, REQUEST_PATIENT_MERGE2, READ_PATIENT_DEMAT
EWPT0002急诊管理
02-ewpt0002-gestion-des-urgences/
READ_EMERGENCY, NEW_EMERGENCY, UPDATE_EMERGENCY, ENDOF_EMERGENCY, CANCEL_ENDOF_EMERGENCY, TO_OUTPATIENT, TO_INPATIENT, DELETE_EMERGENCY
EWPT0003门诊管理
03-ewpt0003-gestion-des-consultations-externes/
NEW_OUTPATIENT, READ_OUTPATIENT, UPDATE_OUTPATIENT, DELETE_OUTPATIENT
EWPT0004住院病案管理
04-ewpt0004-gestion-des-dossiers-d-hospitalisation/
READ_INPATIENT, NEW_INPATIENT, UPDATE_INPATIENT, DELETE_INPATIENT, CONFIRM_PREADMIT, READ_MOVEMENT, NEW_MOVEMENT, UPDATE_MOVEMENT, DELETE_MOVEMENT, CREATE_PENDING_VISIT_MVTS, MOVEMENT_AT, HOSP_BABY
EWPT0005占用情况查询
05-ewpt0005-lecture-des-occupations/
ACTIVE_EMERGENCIES, HOUSING_UF_OCC, UF_OCC, RESPCENTER_OCC, SERVICE_OCC, POLE_OCC, LOCALIZATION_OCC, AVAILABLE_BEDS, IN_HOSPITAL
EWPT0007住院周期管理
07-ewpt0007-gestion-des-sejours/
PATIENT_CASES, CASE_MVTS, MVT_HIST, HOSP_MODE_AT, NEW_HOSP_MODE, UPDATE_HOSP_MODE, DELETE_HOSP_MODE, READ_INFORMED_CONSENT, CHG_CASE_TYPE
EWPT0008产品管理
08-ewpt0008-produits/
INIT_ENV, GET_GEST, GET_FAMILY, GET_UNIT, GET_TAXE, GET_ACCOUNT_NUMBER, GET_UFMAINSTORE, GET_CMP, GET_GROUPING, PRODUCT_VERIFICATION, GET_PRODUCT_NUMBER, PRODUCT_CREATION
EWPT0009DMP管理
09-ewpt0009-gestion-du-dmp/
NEW_REJECTION, UPDATE_REJECTION, ACCESS_CODE, INFO_VITALE, READ_OTP, UPDATE_DMPINFO
EWPT0010执业医师管理
10-ewpt0010-gestion-des-praticiens/
FIND_PRACT, NEW_PRACT, UPDATE_PRACT
EWPT0014物理结构管理
14-ewpt0014-gestion-des-structures/
CHACC_LOCALIZATION, FIND/READ/NEW/UPDATE/DELETE_BUILDING, FIND/READ/NEW/UPDATE/DELETE_FLOOR, FIND/READ/NEW/UPDATE/DELETE_BEDROOM, FIND/READ/NEW/UPDATE/DELETE_BED, FIND/READ/NEW/UPDATE/DELETE_LOCALIZATION
EWPT0012诊疗项目集成
12-ewpt0012-integration-d-actes/
INTEGR_CCAM
EWPT0013身份/流转记录重生成
13-ewpt0013-re-generation-identites-mouvements/
REGEN_IDMVT

Method-to-service quick lookup

方法-服务快速对照表

Use this table to quickly find which page to fetch when the user mentions a method name:
Method patternService page
*_PATIENT*
, 
*_CHILDLINK*
, 
*_KIN*
, 
*_COVERAGE*
, 
*_DOCTOR*
, 
PATIENT_DEBT
, 
*_PROT_*
, 
*_PATIENT_ADDR*
, 
*_PATIENT_MERGE*
, 
*_PATIENT_DEMAT*
, 
LEGAL_REPRESENTATIVES
EWPT0001
*_EMERGENCY*
, 
TO_OUTPATIENT
, 
TO_INPATIENT
EWPT0002
*_OUTPATIENT*
EWPT0003
*_INPATIENT*
, 
*_MOVEMENT*
, 
CONFIRM_PREADMIT
, 
CREATE_PENDING_VISIT_MVTS
, 
MOVEMENT_AT
, 
HOSP_BABY
EWPT0004
*_OCC
, 
ACTIVE_EMERGENCIES
, 
AVAILABLE_BEDS
, 
IN_HOSPITAL
EWPT0005
PATIENT_CASES
, 
CASE_MVTS
, 
MVT_HIST
, 
*_HOSP_MODE*
, 
READ_INFORMED_CONSENT
, 
CHG_CASE_TYPE
EWPT0007
INIT_ENV
, 
GET_*
, 
PRODUCT_*
EWPT0008
*_REJECTION
, 
ACCESS_CODE
, 
INFO_VITALE
, 
READ_OTP
, 
UPDATE_DMPINFO
EWPT0009
*_PRACT*
EWPT0010
*_BUILDING*
, 
*_FLOOR*
, 
*_BEDROOM*
, 
*_BED*
, 
*_LOCALIZATION*
, 
CHACC_LOCALIZATION
EWPT0014
INTEGR_CCAM
EWPT0012
REGEN_IDMVT
EWPT0013
当用户提及方法名时，可使用本表快速定位需要获取的页面：
方法匹配规则所属服务页面
*_PATIENT*
, 
*_CHILDLINK*
, 
*_KIN*
, 
*_COVERAGE*
, 
*_DOCTOR*
, 
PATIENT_DEBT
, 
*_PROT_*
, 
*_PATIENT_ADDR*
, 
*_PATIENT_MERGE*
, 
*_PATIENT_DEMAT*
, 
LEGAL_REPRESENTATIVES
EWPT0001
*_EMERGENCY*
, 
TO_OUTPATIENT
, 
TO_INPATIENT
EWPT0002
*_OUTPATIENT*
EWPT0003
*_INPATIENT*
, 
*_MOVEMENT*
, 
CONFIRM_PREADMIT
, 
CREATE_PENDING_VISIT_MVTS
, 
MOVEMENT_AT
, 
HOSP_BABY
EWPT0004
*_OCC
, 
ACTIVE_EMERGENCIES
, 
AVAILABLE_BEDS
, 
IN_HOSPITAL
EWPT0005
PATIENT_CASES
, 
CASE_MVTS
, 
MVT_HIST
, 
*_HOSP_MODE*
, 
READ_INFORMED_CONSENT
, 
CHG_CASE_TYPE
EWPT0007
INIT_ENV
, 
GET_*
, 
PRODUCT_*
EWPT0008
*_REJECTION
, 
ACCESS_CODE
, 
INFO_VITALE
, 
READ_OTP
, 
UPDATE_DMPINFO
EWPT0009
*_PRACT*
EWPT0010
*_BUILDING*
, 
*_FLOOR*
, 
*_BEDROOM*
, 
*_BED*
, 
*_LOCALIZATION*
, 
CHACC_LOCALIZATION
EWPT0014
INTEGR_CCAM
EWPT0012
REGEN_IDMVT
EWPT0013

Key DTD formats

核心DTD格式

DTDUsed byDescription
RESULT.HEXACALLWAll methodsStandard error/result envelope (code, status, descr, when)
PATIENT_INFO.HEXASERVEWPT0001Patient demographic data
PATPROT.HEXASERVEWPT0001Patient protection data
LIST_PAT.HEXASERVEWPT0001Patient search results
CHILD_LINK.HEXASERVEWPT0001Mother-child link
LIST_COVERAGE.HEXASERVEWPT0001Patient coverage list
LIST_KIN.HEXASERVEWPT0001Patient next-of-kin list
LIST_ADR.HEXASERVEWPT0001Patient addresses
PAT_RMERGE.HEXASERVEWPT0001Patient merge request
LIST_DOCPAT.HEXASERVEWPT0001Dematerialized patient documents
CASE.HEXASERVEWPT0002, EWPT0004Inpatient case/visit + movements
CX_CASE.HEXASERVEWPT0003Outpatient (consultation) case
MVT_CASE.HEXASERVEWPT0004Movement data within a case
LIST_OCC.HEXASERVEWPT0005Occupation list (beds, units)
LIST_BED.HEXASERVEWPT0005Available beds list
LIST_CASE.HEXASERVEWPT0007Patient cases list
LIST_MVT.HEXASERVEWPT0007Movements list for a case
MVT_HIST.HEXASERVEWPT0007Movement history
HOSP_MODE.HEXAGHPEWPT0007Hospitalization mode
INF_CONS.HEXASERVEWPT0007Informed consent
LIST_PRACT.HEXAGHPEWPT0010Practitioner list
DMP_*.HEXASERVEWPT0009DMP-related DTDs
DTD使用方描述
RESULT.HEXACALLW所有方法标准错误/结果封装（代码、状态、描述、时间）
PATIENT_INFO.HEXASERVEWPT0001患者人口统计数据
PATPROT.HEXASERVEWPT0001患者保护数据
LIST_PAT.HEXASERVEWPT0001患者搜索结果
CHILD_LINK.HEXASERVEWPT0001母子关联关系
LIST_COVERAGE.HEXASERVEWPT0001患者医保列表
LIST_KIN.HEXASERVEWPT0001患者亲属列表
LIST_ADR.HEXASERVEWPT0001患者地址
PAT_RMERGE.HEXASERVEWPT0001患者合并请求
LIST_DOCPAT.HEXASERVEWPT0001患者电子化文档
CASE.HEXASERVEWPT0002, EWPT0004住院病案/就诊 + 流转记录
CX_CASE.HEXASERVEWPT0003门诊（问诊）病案
MVT_CASE.HEXASERVEWPT0004病案内流转数据
LIST_OCC.HEXASERVEWPT0005占用列表（床位、单元）
LIST_BED.HEXASERVEWPT0005可用床位列表
LIST_CASE.HEXASERVEWPT0007患者病案列表
LIST_MVT.HEXASERVEWPT0007病案流转列表
MVT_HIST.HEXASERVEWPT0007流转历史
HOSP_MODE.HEXAGHPEWPT0007住院模式
INF_CONS.HEXASERVEWPT0007知情同意书
LIST_PRACT.HEXAGHPEWPT0010执业医师列表
DMP_*.HEXASERVEWPT0009DMP相关DTD

How to answer questions

如何回答问题

Step 1: Identify the relevant page

步骤1：定位相关页面

Map the user's question to one or more service pages using the tables above:
  • Specific method name (e.g., "READ_PATIENT") → use the method-to-service lookup
  • Domain keyword (e.g., "patient", "urgence", "hospitalisation") → match to the service catalog
  • DTD name (e.g., "CASE.HEXASERV") → use the DTD table to find the service page
  • Error handling / general architecture → fetch the Introduction page
  • General "list all services" → use the catalog above, no fetch needed
使用上表将用户的问题映射到一个或多个服务页面：
  • 特定方法名（例如「READ_PATIENT」）→ 使用方法-服务对照表
  • 领域关键词（例如「patient」、「urgence」、「hospitalisation」）→ 匹配服务目录
  • DTD名称（例如「CASE.HEXASERV」）→ 使用DTD表查找服务页面
  • 错误处理 / 通用架构 → 获取介绍页面
  • 通用「列出所有服务」需求 → 使用上面的目录即可，无需获取页面

Step 2: Fetch the page

步骤2：获取页面内容

Use the WebFetch tool to retrieve the relevant page:
WebFetch: url="${BASE_URL}<page-path>" format="markdown"
For example:
  • Introduction: 
    WebFetch: url="https://erp-pas.gitlab-pages-erp-pas.dedalus.lan/hexagone/swdoc/00-introduction/" format="markdown"
  • Patient management: 
    WebFetch: url="https://erp-pas.gitlab-pages-erp-pas.dedalus.lan/hexagone/swdoc/01-ewpt0001-gestion-des-patients/" format="markdown"
Fetch only the page(s) you need. Do not fetch all pages at once -- each service page can be large.
If WebFetch fails (network error, timeout), inform the user that the GitLab Pages site is unreachable and suggest they access it directly in their browser.
使用WebFetch工具获取相关页面：
WebFetch: url="${BASE_URL}<page-path>" format="markdown"
示例：
  • 介绍页：
    WebFetch: url="https://erp-pas.gitlab-pages-erp-pas.dedalus.lan/hexagone/swdoc/00-introduction/" format="markdown"
  • 患者管理页：
    WebFetch: url="https://erp-pas.gitlab-pages-erp-pas.dedalus.lan/hexagone/swdoc/01-ewpt0001-gestion-des-patients/" format="markdown"
仅获取你需要的页面。不要一次性获取所有页面，每个服务页面的体积可能很大。
如果WebFetch执行失败（网络错误、超时），告知用户GitLab Pages站点无法访问，建议他们直接在浏览器中访问该站点。

Step 3: Extract and present the answer

步骤3：提取并呈现答案

After fetching, extract the relevant section from the page content:
  1. For a specific method: find the 
    Méthode <NAME>
    section, extract parameters, SOAP interface, and related DTD
  2. For a DTD format: find the 
    DTD <NAME>
    section, extract all field definitions
  3. For error codes: find the 
    Gestion des codes retour et statuts
    section
  4. For configuration: find the 
    Configuration de l'application
    section
Present the information clearly. Preserve the original structure (parameter tables, DTD field lists, error code tables) from the documentation.
获取页面后，从页面内容中提取相关部分：
  1. 针对特定方法：查找
    Méthode <NAME>
    章节，提取参数、SOAP接口和相关DTD
  2. 针对DTD格式：查找
    DTD <NAME>
    章节，提取所有字段定义
  3. 针对错误代码：查找
    Gestion des codes retour et statuts
    章节
  4. 针对配置：查找
    Configuration de l'application
    章节
清晰呈现信息，保留文档中的原始结构（参数表、DTD字段列表、错误代码表）。

Step 4: Cross-reference if needed

步骤4：必要时交叉引用

If the user's question spans multiple services (e.g., "how do I create an emergency case and then transfer to inpatient?"), fetch multiple pages and compose a coherent answer showing the workflow across services.
如果用户的问题涉及多个服务（例如「如何创建急诊病案然后转住院？」），获取多个页面并整理出连贯的答案，说明跨服务的工作流程。

Response guidelines

响应规范

When presenting web service documentation, keep the original structure from the fetched page. Hexagone web services follow a consistent pattern:
markdown
undefined
呈现Web服务文档时，保留获取页面的原始结构。Hexagone Web服务遵循统一的格式：
markdown
undefined

Méthode <METHOD_NAME>

Méthode <METHOD_NAME>

Service: EWPT000X – <Domain> Source: [page URL]
服务: EWPT000X – <领域> 来源: [页面URL]

Description

描述

[What the method does]
[方法功能说明]

Parameters

参数

TypeNameDirectionRequiredDescription
stringapplicationINYesCaller application ID
...............
类型名称方向必填描述
stringapplication入参是调用方应用ID
...............

SOAP Interface

SOAP接口

[Request/Response message structure]
[请求/响应消息结构]

Related DTD

关联DTD

[XML format used for data exchange]
[数据交换使用的XML格式]

Error Codes

错误代码

[Specific error codes for this method, if any]
[本方法特有的错误代码（如有）]

Configuration

配置

[Required application configuration, if any]
undefined
[所需的应用配置（如有）]
undefined

Important rules

重要规则

  1. Always fetch from the GitLab Pages site -- never answer from memory or general knowledge about web services. The Hexagone API has specific conventions, SOAP-based interfaces with XML DTDs, that do not follow standard REST patterns.
  2. Quote the source URL when presenting information: always mention which page the information comes from (e.g., "Source: EWPT0001 -- Gestion des patients").
  3. Do not invent methods or parameters -- if the information is not found on the fetched page, say so explicitly. Do not guess or extrapolate.
  4. Handle missing documentation gracefully -- if a method is not documented, inform the user and suggest they check with the Hexagone development team or open an issue in the swdoc repository at 
    https://gitlab-erp-pas.dedalus.lan/erp-pas/hexagone/swdoc
    .
  5. Respect the source of truth -- if there is a conflict between what the user believes and what the documentation says, trust the documentation and point out the discrepancy.
  6. Cross-reference with HPK/HL7 -- if the web service relates to interoperability messages (HPK, HL7), mention the connection and suggest using the 
    hpk-parser
    or 
    hl7-pam-parser
    skills for message-level details.
  7. Common patterns to highlight:
    • All methods require an 
      application
      parameter (caller identification, configured in Hexagone Web)
    • All methods return a 
      result
      buffer in 
      RESULT.HEXACALLW
      format (code + status + description)
    • Code 
      0
      = success; any other code = error (check status for details)
    • Data exchange uses XML buffers with specific DTD formats per domain
    • Application configuration (CODEGEST, PSACC, etc.) affects behavior per caller
  1. 始终从GitLab Pages站点获取内容 -- 绝对不要依赖记忆或Web服务相关的通用知识作答。Hexagone API有特殊的约定，基于SOAP的接口搭配XML DTD，并不遵循标准的REST模式。
  2. 呈现信息时标注来源URL：始终说明信息来自哪个页面（例如「来源：EWPT0001 -- 患者管理」）。
  3. 不要虚构方法或参数 -- 如果获取的页面中没有相关信息，明确告知用户。不要猜测或推断。
  4. 优雅处理缺失的文档 -- 如果某个方法没有文档，告知用户并建议他们联系Hexagone开发团队，或在swdoc仓库提交issue：
    https://gitlab-erp-pas.dedalus.lan/erp-pas/hexagone/swdoc
    。
  5. 尊重事实来源 -- 如果用户的认知与文档内容存在冲突，以文档为准并指出差异。
  6. 关联HPK/HL7内容 -- 如果该Web服务涉及互操作消息（HPK、HL7），说明关联关系并建议使用
    hpk-parser
    或
    hl7-pam-parser
    技能获取消息层面的细节。
  7. 需要突出的通用规则：
    • 所有方法都需要
      application
      参数（调用方标识，在Hexagone Web中配置）
    • 所有方法都会返回
      RESULT.HEXACALLW
      格式的
      result
      缓冲区（代码 + 状态 + 描述）
    • 代码
      0
      = 成功；其他任何代码 = 错误（查看状态获取详情）
    • 数据交换使用XML缓冲区，不同领域对应特定的DTD格式
    • 应用配置（CODEGEST、PSACC等）会影响不同调用方的行为