FHIR搜索广告位请求 [英] FHIR Search Slots request

查看:136
本文介绍了FHIR搜索广告位请求的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我正在使用FHIR服务器,由于某些不可避免的原因,我无法访问医生的日程安排,但是,我可以访问可用于预约的空位.

I am implementing FHIR server and for some un-avoidable reason I do not have access to doctor's schedule, however, I have access to the slots available for appointment booking.

我可以使用以下4个参数获取广告位

I can get slots from 4 parameters using

  1. 医生编号
  2. 组织编号
  3. 位置ID
  4. 广告位日期
  1. doctor id
  2. organization id
  3. location id
  4. date of slot

以下将被视为使用FHIR的有效广告位查询:

Will below be considered as valid slot query using FHIR :

http://localhost:8080/context/fhir/Slot?practitioner = Practitioner/123456789& organization = Organization/1234& location = Location/2& start = 2016-07-25

另外,在对以上查询的响应中,由于绝对需要引用Schedule(插槽对于时间表引用,卡具有card = 1..1),我可以像这样传递参考值:

Also, in the response to above query, since reference to Schedule is absolutely necessary (Slot has card=1..1 for Schedule reference), can I pass reference value as something like :

"schedule": {
    "reference": "Schedule/notrequired"
  }

在广告位响应中?

推荐答案

不幸的是,现在,您确实必须公开一个Schedule,但没有任何理由必须是真实的".我们当前实现的广告位搜索方式是通过公开一个虚拟Schedule,其中唯一的数据元素是与actor的链接.例如:

Unfortunately, right now, you do have to expose a Schedule, but there isn't any reason it has to be "real". The way we have currently implemented Slot searching is by exposing a dummy Schedule with the only data element being the link to the actor. For example:

<Schedule xmlns="http://hl7.org/fhir">
<id value="1234" />
<actor>
    <display value="Cooper Thompson, MD" />
    <reference value="http://host/api/FHIR/DSTU2/Practitioner/1234" />
</actor>

我们的广告位搜索最终看起来像这样(为简洁起见,进行了一些编辑,特别是围绕广告位类型):

Our Slot search ends up looking like this (with some edits for brevity and clarity, specifically around the slottype):

http://host/api/FHIR/DSTU2/Slot?Schedule.actor:Practitioner=1234&Schedule.actor:Patient=5678&slottype=urn:oid:1.2.3|Cardiology&start=2016-07-21

请注意,这在技术上是无效的,因为广告位只能有一个Schedule,并且我们为Schedule添加了多个链接的搜索参数.由于Slot.schedule为1:1,因此我们还利用扩展名将与该插槽关联的患者,医生和位置发回给您.但是,这种故意滥用"是我发现的最佳选择,而不会强迫客户端成为调度系统并处理每个资源的排队时间.

Note that this is technically invalid, as a Slot can only have one Schedule, and we are including multiple chained search parameters for Schedule. We also make use of extensions to send back the patient, practitioner, and location associated with the slot, since Slot.schedule is 1:1. However this "intentional misuse" is the best option I've found without forcing the client to become the scheduling system and deal with lining up slots for each resource.

有些跟踪器项目( 9989 9208 )在FHIR gforge中讨论了如何对Slot进行更新,使其对简单客户端"更加友好.非常感谢您的输入:).

There are some tracker items (9989, 9208) in the FHIR gforge about making updates to Slot to be more friendly to "simple clients". We'd appreciate your input :).

这篇关于FHIR搜索广告位请求的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆