简体繁体 English

如何将HL7 v2转换为FHIR

[英]How to convert HL7 v2 to FHIR

原文 2016-10-31 19:16:02 4 1 adt/ hl7/ hl7-fhir

We'd like to replace HL7 v2 A01 transactions with FHIR resource transactions, and want to know what the options are to map A01 to FHIR resources. 我们想用FHIR资源事务替换HL7 v2 A01事务，并想知道将A01映射到FHIR资源的选项。 Based on researches through the docs and discussions, there two potential options stand out to me: 根据对文档和讨论的研究，我有两个可能的选择：

(a) map ADT to Encounter with extensions for children resource references （a）将ADT映射到Encounter，并附带子项资源引用的扩展名
(b) model ADT as FHIR messaging process with a bundle of several resources and linkage info （b）将ADT模型化为FHIR消息传递过程，其中包含多个资源和链接信息

What are your recommendations? 你有什么建议？

Thanks 谢谢

1 个解决方案

Ultimately the answer will depend on how you want the message to be interpreted. 最终答案取决于您希望如何解释消息。 An ADT^A01 message is event-based, and if you want to convey that the event has happened using FHIR, messaging is the best fit. ADT ^ A01消息是基于事件的，如果您想使用FHIR表示事件已经发生，则消息传递是最合适的。 This assumes that the receiving system(s) has a stateful model of ADT where messages will be received an interpreted correctly. 这假设接收系统具有ADT的有状态模型，其中将正确解释接收消息。

HL7 hasn't formalized ADT events as part of the messaging events in FHIR . HL7尚未将ADT事件正式化为FHIR中的消息传递事件的一部分。 As a casual onlooker I would classify ADT^A01 into the category of an event with a consequence see section 2.24.1.1 作为一个随意的旁观者，我会将ADT ^ A01归类为事件类别，结果见2.24.1.1节

The message represents/requests a change that should not be processed more than once; 该消息表示/请求不应多次处理的更改; eg, making a booking for an appointment. 例如，预约预约。

If you only care about demographics updates - you may be betters served by cherry-picking fields from HL7v2 and using REST to push updates. 如果您只关心人口统计信息更新 - 您可能会更好地使用来自HL7v2的樱桃挑选字段并使用REST推送更新。