FHIR ExplanationOfBenefit中discharge-status字段数据缺失原因添加方法咨询

• 遵循FHIR核心规范处理缺失值：
  FHIR允许通过dataAbsentReason字段明确数据缺失原因，对于C4BB定义的discharge-status切片，即使value（出院状态编码）为空，也需保留该supportingInfo条目结构，添加dataAbsentReason说明原因，不能直接省略整个条目。

• 选择匹配业务场景的缺失原因代码：
  从FHIR标准的DataAbsentReason值集中选取对应代码，常见选项包括：

  • unknown：出院状态未知
  • not-collected：未收集该信息
  • not-applicable：当前场景下出院状态不适用（如患者未完成出院流程）

• BigQuery SQL实现示例：
  假设你的原始理赔表为raw_outpatient_claims，其中discharge_status字段可能为空，构建FHIR结构时可通过CASE分支处理：

  SELECT
    -- 填充ExplanationOfBenefit其他必填字段...
    ARRAY(
      SELECT AS STRUCT
        -- 标记为discharge-status切片
        STRUCT(
          ARRAY(STRUCT(
            'discharge-status' AS code,
            'Discharge Status' AS display,
            'http://hl7.org/fhir/us/carin-bb/CodeSystem/C4BBSupportingInfoType' AS system
          )) AS coding
        ) AS category,
        -- 处理出院状态值
        CASE WHEN rc.discharge_status IS NOT NULL THEN
          STRUCT(
            ARRAY(STRUCT(
              rc.discharge_status AS code,
              (SELECT display FROM nubc_patient_status WHERE code = rc.discharge_status) AS display,
              'http://nubc.org/patient-status' AS system
            )) AS coding
          ) AS valueCodeableConcept
        ELSE NULL END AS valueCodeableConcept,
        -- 添加数据缺失原因
        CASE WHEN rc.discharge_status IS NULL THEN
          STRUCT(
            ARRAY(STRUCT(
              'unknown' AS code, -- 根据实际场景替换为对应代码
              'Unknown' AS display,
              'http://hl7.org/fhir/data-absent-reason' AS system
            )) AS coding
          ) AS dataAbsentReason
        ELSE NULL END AS dataAbsentReason
      FROM UNNEST([STRUCT(rc.discharge_status)]) rc
    ) AS supportingInfo
  FROM raw_outpatient_claims
  

• 验证合规性：
  确认supportingInfo条目的category编码正确对应discharge-status切片；当valueCodeableConcept为空时，dataAbsentReason必须存在且属于FHIR标准值集，避免因缺失该字段导致资源不符合C4BB结构定义。

内容的提问来源于stack exchange，提问作者Aishwary Shukla