The US Core FHIR Profiles Have One Major Problem!

แชร์
ฝัง
  • เผยแพร่เมื่อ 12 ก.ย. 2024

ความคิดเห็น • 11

  • @medblocks
    @medblocks  4 หลายเดือนก่อน

    If you're a developer this one's for you! Learn how to work with FHIR 🔥.Watch my exclusive webinar here: link.medblocks.com/fhir-53d6ca

    • @devagupta4u
      @devagupta4u 3 หลายเดือนก่อน

      when is ur next openehr bootcamp? pls reply

    • @medblocks
      @medblocks  3 หลายเดือนก่อน

      @@devagupta4u Hey sorry, I'm currently busy with the FHIR Bootcamp. Please add yourself to the waiting list - medblocks.com/openehr-bootcamp and I'll announce on email as soon as we plan a new batch.

  • @peterjordan6608
    @peterjordan6608 3 หลายเดือนก่อน

    It would be helpful to use the correct element names - e.g. Observation.bodySite rather than 'location'. In FHIR a Location is a HealthCare Facility not a body site. Many (most?) of the copious openEHR archetype properties for a blood pressure observation belong in FHIR extensions as per the '80/20' rule.

  • @Shamil-qx6dg
    @Shamil-qx6dg 3 หลายเดือนก่อน

    So, are you basically saying that a Cerner developer was too lazy to click the _Snapshot Table_ to see all elements derived from the original _Observation_ resource?

    • @medblocks
      @medblocks  3 หลายเดือนก่อน

      Just might be the case. Either way, this is a valid FHIR resource in compliance with the US Core IG somehow because none of the elements in the expended snapshot table (body site) were "must support"

  • @devagupta4u
    @devagupta4u 3 หลายเดือนก่อน

    @Sidharth Ramesh when is ur next openehr bootcamp? pls reply

    • @medblocks
      @medblocks  3 หลายเดือนก่อน

      Hey sorry, I'm currently busy with the FHIR Bootcamp. Please add yourself to the waiting list - medblocks.com/openehr-bootcamp and I'll announce on email as soon as we plan a new batch.