Schema.org COVID-19 响应:美国CDC医院数据标准化方案解析
This document details Schema.org's structured vocabulary extension for encoding US CDC COVID-19 hospital reporting data, enabling standardized, machine-readable exchange of key metrics like bed counts, ventilator usage, and patient statistics. (本文档详细介绍了Schema.org为编码美国CDC COVID-19医院报告数据而扩展的结构化词汇表,旨在实现床位数量、呼吸机使用情况和患者统计等关键指标的标准化、机器可读的数据交换。)
Introduction
In the early stages of the COVID-19 pandemic, the need for timely, structured, and interoperable data on hospital capacity and patient outcomes became critically important. To facilitate the collection and exchange of this vital information, the US Centers for Disease Control and Prevention (CDC) defined a specific data format for hospital reporting. This technical document outlines how the Schema.org vocabulary was extended to provide a standards-based, machine-readable representation of the CDC's COVID-19 Patient Module Denominator data format. This allows the critical data defined by public health authorities to be seamlessly integrated into the broader ecosystem of structured data on the web.
在 COVID-19 大流行的早期阶段,及时获取关于医院收治能力和患者结果的、结构化的、可互操作的数据变得至关重要。为了促进这一关键信息的收集和交换,美国疾病控制与预防中心(CDC)为医院报告定义了一种特定的数据格式。本文档从技术层面阐述了如何扩展 Schema.org 词汇表,以提供一种基于标准的、机器可读的 CDC COVID-19 患者模块分母数据格式表示方法。这使得公共卫生当局定义的关键数据能够无缝集成到更广泛的网络结构化数据生态系统中。
Purpose and Scope
The primary goal of this Schema.org extension is to create a faithful, round-trippable representation of the CDC's tabular data specification. It introduces a new structured data type, CDCPMDRecord, along with a set of properties prefixed with cvd, to correspond directly to each field in the CDC's original format. This enables the encoding of hospital census data—such as bed counts, ventilator usage, and COVID-19 patient statistics—in formats like JSON-LDA lightweight Linked Data format for structuring data in JSON, recommended by Google for Schema.org implementation., Microdata, or RDFa. It is crucial to note that this schema is designed for data exchange and interoperability in various technical contexts; it does not imply that such data should be publicly published for search engine consumption, nor does it supersede the authoritative definitions and updates provided by the CDC.
此 Schema.org 扩展的主要目标是创建对 CDC 表格数据规范的忠实、可往返的表示。它引入了一个新的结构化数据类型
CDCPMDRecord,以及一组以cvd为前缀的属性,以直接对应 CDC 原始格式中的每个字段。这使得医院普查数据——如床位数量、呼吸机使用情况和 COVID-19 患者统计——能够以 JSON-LDA lightweight Linked Data format for structuring data in JSON, recommended by Google for Schema.org implementation.、Microdata 或 RDFa 等格式进行编码。必须注意,此模式设计用于各种技术上下文中的数据交换和互操作性;它并不意味着此类数据应公开发布供搜索引擎使用,也不取代 CDC 提供的权威定义和更新。
Source Documentation:
- Title: Importing COVID-19 Patient Module Denominator data for Patient Safety Component (PSC)
- URL: https://www.cdc.gov/nhsn/pdfs/covid19/import-covid19-data-508.pdf
源文档:
- 标题: 为患者安全组件导入 COVID-19 患者模块分母数据
- URL: https://www.cdc.gov/nhsn/pdfs/covid19/import-covid19-data-508.pdf
Core Vocabulary Extensions
To model the CDC data format, several new terms were added to the Schema.org vocabulary within its "Pending" area, allowing for community review and implementation feedback before full integration.
为了对 CDC 数据格式进行建模,在 Schema.org 词汇表的 "Pending" 区域中添加了几个新术语,以便在完全集成之前进行社区审查和实施反馈。
New Type: CDCPMDRecord
A new type CDCPMDRecord was created as a subtype of StructuredValue. This type serves as the container for all data points related to a single reporting instance from a healthcare facility.
创建了一个新类型
CDCPMDRecord作为StructuredValue的子类型。此类型用作容纳来自医疗机构单次报告实例的所有数据点的容器。
- Schema.org Path:
Thing > Intangible > StructuredValue > CDCPMDRecord - 中文释义: 事物 > 无形 > 结构化值 > CDC患者模块分母记录
New Properties
Fourteen new properties were introduced, each mapping directly to a field in the CDC specification. Most expect a Number value with constraints (e.g., 0-10000) as defined by the CDC. The cvd prefix was used to prevent naming conflicts with existing Schema.org properties (e.g., numberOfBeds is used for hotels).
引入了十四个新属性,每个都直接映射到 CDC 规范中的一个字段。大多数属性期望一个
Number类型的值,并带有 CDC 定义的约束(例如,0-10000)。使用cvd前缀是为了防止与现有的 Schema.org 属性(例如,numberOfBeds用于酒店)发生命名冲突。
The key properties include:
关键属性包括:
cvdCollectionDate(Text): The date for which patient counts are reported. While the CDC uses mm/dd/yyyy, ISO 8601 format is also supported to avoid ambiguity.- 中文: 报告患者数量的日期。CDC 使用 mm/dd/yyyy 格式,但也支持 ISO 8601 格式以避免歧义。
cvdNumBeds(Number): Total staffed, licensed, and surge inpatient beds.- 中文: 配备人员、有执照及应急使用的总住院床位。
cvdNumICUBeds(Number): Total staffed inpatient ICU beds.- 中文: 配备人员的总住院ICU床位。
cvdNumVent(Number): Total number of ventilators available.- 中文: 可用的呼吸机总数。
cvdNumC19HospPats(Number): Patients currently hospitalized with suspected or confirmed COVID-19.- 中文: 当前住院的疑似或确诊 COVID-19 患者。
cvdNumC19Died(Number): Patients with suspected or confirmed COVID-19 who died in the hospital, ED, or overflow location.- 中文: 在医院、急诊室或溢出区域死亡的疑似或确诊 COVID-19 患者。
(The list above is a subset. The full table is detailed in the next section.)
(以上列表是子集。完整表格详见下一节。)
Relational Property
To link this data to a specific healthcare facility, a new property was also added:
为了将这些数据链接到特定的医疗机构,还添加了一个新属性:
healthcareReportingData: This property can be used on aHospitaltype to point to one or moreCDCPMDRecordobjects, establishing the relationship between the institution and its reported data.- 中文: 此属性可用于
Hospital类型,指向一个或多个CDCPMDRecord对象,从而建立机构与其报告数据之间的关系。
- 中文: 此属性可用于
Field Mapping Reference
The table below provides the authoritative mapping from the CDC field names to the new Schema.org properties, including expected value types and critical notes summarizing CDC-defined constraints. For all formal interpretation, always refer to the source CDC documentation.
下表提供了从 CDC 字段名到新 Schema.org 属性的权威映射,包括期望值类型和总结 CDC 定义约束的关键说明。对于所有正式解释,请务必参考 CDC 源文档。
| CDC Field Name | Schema.org Property | Expected Value | Notes (Summary) | Definition |
|---|---|---|---|---|
| collectiondate | cvdCollectionDate |
Text | CDC required. Original format: mm/dd/yyyy. ISO 8601 is also acceptable. | Date for which patient counts are reported. |
| numbeds | cvdNumBeds |
Number | 0-10000, integer. Must be <= cvdNumTotBeds. |
HOSPITAL INPATIENT BEDS: Inpatient beds, including all staffed, licensed, and overflow (surge) beds used for inpatients. |
| numtotbeds | cvdNumTotBeds |
Number | 0-10000, integer. | ALL HOSPITAL BEDS: Total number of all Inpatient and outpatient beds, including all staffed, ICU, licensed, and overflow (surge) beds. |
| numbedsocc | cvdNumBedsOcc |
Number | 0-10000, integer. Must be <= cvdNumBeds. |
HOSPITAL INPATIENT BED OCCUPANCY: Total number of staffed inpatient beds that are occupied. |
| numicubeds | cvdNumICUBeds |
Number | 0-10000, integer. Must be <= cvdNumBeds. |
ICU BEDS: Total number of staffed inpatient intensive care unit (ICU) beds. |
| numicubedsocc | cvdNumICUBedsOcc |
Number | 0-10000, integer. Must be <= cvdNumICUBeds. |
ICU BED OCCUPANCY: Total number of staffed inpatient ICU beds that are occupied. |
| numvent | cvdNumVent |
Number | 0-10000, integer. Must be <= cvdNumTotBeds or <= 10,000. |
MECHANICAL VENTILATORS: Total number of ventilators available. |
| numventuse | cvdNumVentUse |
Number | 0-10000, integer. Must be <= cvdNumVent or <= 10,000. |
MECHANICAL VENTILATORS IN USE: Total number of ventilators in use. |
| numc19hosppats | cvdNumC19HospPats |
Number | 0-10000, integer. Must be <= cvdNumBedsOcc. |
HOSPITALIZED: Patients currently hospitalized in an inpatient care location who have suspected or confirmed COVID-19. |
| numc19mechventpats | cvdNumC19MechVentPats |
Number | 0-10000, integer. Must be <= cvdNumVentUse. |
HOSPITALIZED and VENTILATED: Patients hospitalized in an NHSN inpatient care location who have suspected or confirmed COVID-19 and are on a mechanical ventilator. |
| numc19hopats | cvdNumC19HOPats |
Number | 0-10000, integer. Must be <= cvdNumBedsOcc. |
HOSPITAL ONSET: Patients hospitalized in an NHSN inpatient care location with onset of suspected or confirmed COVID-19 14 or more days after hospitalization. |
| numc19overflowpats | cvdNumC19OverflowPats |
Number | 0-2000, integer. Must be <=2000. | ED/OVERFLOW: Patients with suspected or confirmed COVID-19 who are in the ED or any overflow location awaiting an inpatient bed. |
| numc19ofmechventpats | cvdNumC19OFMechVentPats |
Number | 0-10000, integer. Must be <= cvdNumVentUse. |
ED/OVERFLOW and VENTILATED: Patients with suspected or confirmed COVID-19 who are in the ED or any overflow location awaiting an inpatient bed and on a mechanical ventilator. |
| numc19died | cvdNumC19Died |
Number | 0-1500, integer. Must be <= 1500. | DEATHS: Patients with suspected or confirmed COVID-19 who died in the hospital, ED, or any overflow location. |
CDC 字段名 Schema.org 属性 期望值 说明(摘要) 定义 collectiondate cvdCollectionDate文本 CDC 要求。原始格式:mm/dd/yyyy。ISO 8601 也可接受。 报告患者数量的日期。 numbeds cvdNumBeds数字 0-10000,整数。必须 <= cvdNumTotBeds。医院住院床位:住院床位,包括所有配备人员、有执照及用于住院患者的应急床位。 numtotbeds cvdNumTotBeds数字 0-10000,整数。 所有医院床位:所有住院和门诊床位的总数,包括所有配备人员、ICU、有执照及应急的床位。 numbedsocc cvdNumBedsOcc数字 0-10000,整数。必须 <= cvdNumBeds。医院住院床位占用率:被占用的配备人员的住院床位总数。 numicubeds cvdNumICUBeds数字 0-10000,整数。必须 <= cvdNumBeds。ICU床位:配备人员的住院重症监护病房床位总数。 numicubedsocc cvdNumICUBedsOcc数字 0-10000,整数。必须 <= cvdNumICUBeds。ICU床位占用率:被占用的配备人员的住院ICU床位总数。 numvent cvdNumVent数字 0-10000,整数。必须 <= cvdNumTotBeds或 <= 10,000。机械呼吸机:可用呼吸机总数。 numventuse cvdNumVentUse数字 0-10000,整数。必须 <= cvdNumVent或 <= 10,000。使用中的机械呼吸机:正在使用的呼吸机总数。 numc19hosppats cvdNumC19HospPats数字 0-10000,整数。必须 <= cvdNumBedsOcc。住院患者:当前在住院护理地点住院的疑似或确诊 COVID-19 患者。 numc19mechventpats cvdNumC19MechVentPats数字 0-10000,整数。必须 <= cvdNumVentUse。住院并使用呼吸机的患者:在 NHSN 住院护理地点住院、疑似或确诊 COVID-19 并使用机械呼吸机的患者。 numc19hopats cvdNumC19HOPats数字 0-10000,整数。必须 <= cvdNumBedsOcc。医院发病:住院 14 天或更长时间后,在 NHSN 住院护理地点发生疑似或确诊 COVID-19 的患者。 numc19overflowpats cvdNumC19OverflowPats数字 0-2000,整数。必须 <=2000。 急诊/溢出:在急诊室或任何等待住院床位的溢出地点的疑似或确诊 COVID-19 患者。 numc19ofmechventpats cvdNumC19OFMechVentPats数字 0-10000,整数。必须 <= cvdNumVentUse。急诊/溢出并使用呼吸机:在急诊室或任何等待住院床位的溢出地点、疑似或确诊 COVID-19 并使用机械呼吸机的患者。 numc19died cvdNumC19Died数字 0-1500,整数。必须 <= 1500。 死亡:在医院、急诊室或溢出地点死亡的疑似或确诊 COVID-19 患者。
Implementation Example (JSON-LDA lightweight Linked Data format for structuring data in JSON, recommended by Google for Schema.org implementation.)
The following is a simplified example of how a CDCPMDRecord could be encoded using JSON-LDA lightweight Linked Data format for structuring data in JSON, recommended by Google for Schema.org implementation., the recommended serialization format due to its flexibility and widespread adoption.
以下是一个简化示例,展示了如何使用 JSON-LDA lightweight Linked Data format for structuring data in JSON, recommended by Google for Schema.org implementation.(因其灵活性和广泛采用而被推荐的序列化格式)对
CDCPMDRecord进行编码。
{
"@context": "https://schema.org",
"@type": "CDCPMDRecord",
"cvdCollectionDate": "2020-04-01",
"cvdFacilityId": "NHSN-12345",
"cvdNumBeds": 250,
"cvdNumTotBeds": 300,
"cvdNumBedsOcc": 200,
"cvdNumICUBeds": 30,
"cvdNumICUBedsOcc": 28,
"cvdNumVent": 25,
"cvdNumVentUse": 20,
"cvdNumC19HospPats": 45,
"cvdNumC19MechVentPats": 15,
"cvdNumC19Died": 2,
"datePosted": "2020-04-02T10:00:00-05:00"
}
A Hospital entity can then link to this record using the healthcareReportingData property, providing clear context.
随后,
Hospital实体可以使用healthcareReportingData属性链接到此记录,从而提供清晰的上下文。
{
"@context": "https://schema.org",
"@type": "Hospital",
"name": "Example General Hospital",
"healthcareReportingData": {
"@type": "CDCPMDRecord",
"cvdCollectionDate": "2020-04-01",
"cvdNumC19HospPats": 45
// ... other relevant properties
}
}
Important Considerations for Implementors
- Authoritative Source: The Schema.org definitions are a representation of the CDC specification. The CDC documentation remains the sole authoritative source for field definitions, value constraints, and updates. Implementors must monitor the CDC site for changes.
- Data Privacy and Publication: This schema enables standardized encoding. It does not mandate where or how the data is stored or published. Sensitive healthcare data must be handled according to applicable laws and regulations (e.g., HIPAA in the US).
- Temporal Nature: This vocabulary was developed in response to a specific, urgent public health need in early 2020. The underlying CDC reporting requirements
版权与免责声明:本文仅用于信息分享与交流,不构成任何形式的法律、投资、医疗或其他专业建议,也不构成对任何结果的承诺或保证。
文中提及的商标、品牌、Logo、产品名称及相关图片/素材,其权利归各自合法权利人所有。本站内容可能基于公开资料整理,亦可能使用 AI 辅助生成或润色;我们尽力确保准确与合规,但不保证完整性、时效性与适用性,请读者自行甄别并以官方信息为准。
若本文内容或素材涉嫌侵权、隐私不当或存在错误,请相关权利人/当事人联系本站,我们将及时核实并采取删除、修正或下架等处理措施。 也请勿在评论或联系信息中提交身份证号、手机号、住址等个人敏感信息。