I am new to FHIR
How to create a Provider information (XML) using HL7-FHIR standard ? do we have any xsd reference to create the provider information
Any help is really appreciated.
Information about healthcare providers (and anyone acting in their professional capacity including receptionists, taxi drivers, etc.) is shared using the Practitioner resource. If you do a search on that page, you'll find links to the XML and JSON schemas.
If you want to build a Health Provider Directory/Index you can have a look at existing Implementation Guides:
Mobile Care Services Discovery
is a IHE profile which implements a HPD with FHIR
Validated Healthcare Directory Implementation Guide
is a FHIR Implementation Guide for a Health Directory
If you compare these two you'll see a common approach on how to represent Paracticioners, Organizations, etc.
Related
I am building a SMART on FHIR app for patient mediated EHR analysis.
Is there a centralized list of SMART on FHIR endpoints? For example, Epic provides this list of endpoints, and a very nice patient facing website to access Epic MyChart for a particular clinic. It is searchable by location. So I can search for "Maryland" and see all clinics with MyChart for that state.
I seek to replicate the Epic MyChart access page, but add SMART on FHIR endpoints from eClinicalWorks, Cerner, and other vendors. I think a central and continually updated list of SMART on FHIR endpoints would be beneficial to EHR interoperability - especially if it were open source and updated frequently. The information is all public, it would be a matter of compiling it and keeping it updated. Is there such a list that already exists?
Right now we are working on a specification to provide more consistent publication of endpoint and branding information to help patients select their provider. We are aiming to have each vendor openly publish more complete data in a consistent format. From there, compiling a centralized list should be possible.
Feel free to check out https://hackmd.io/#argonaut/patient-access-brands for details.
Probably not quite what you're after, but I wanted to point out that Lantern aggregates published FHIR API endpoints and some details about them.
Can somehow explain me the difference in these products?
As far as I understand IBM ACE (AppConnect) gives you more or iPaas capabalities. It is allows you to make an API.
But from what I understand now is that API Connect is required for the actual API management. Proxy/policies etc.
Does anyone know you these products are licensed? Do you have to API connect for your APIs to be managed, governed etc?
This is not an exhaustive answer, but hopefully it'll point you in the right direction...
App Connect is for building integrations (flows) with various data sources. Could be databases, cloud services like GSuite or Salesforce, or even HTTP endpoints. Those flows could be triggered by events in one of those systems or by an API. You can also do things like turn a database schema into an API. You get the idea.
API Connect is for API governance, security, and socialization. In more concrete terms, it gives you tools for things like: adding authentication and/or authorization to all APIs, bundling APIs together, enforcing rate limits or quotas, providing a portal for sharing/selling your APIs with others, and so on.
You can create APIs using App Connect and stop there--it's usable/invokable without API Connect in the picture. API Connect provides enforcement policies to give you more flexibility in how you call that API and/or give others the ability to invoke the API. The two products complement each other, but an API management product would be required in order to manage and govern the APIs created by App Connect.
In terms of licensing, there are multiple available options. You can purchase the products as standalone software packages that you install and maintain yourself (see IBM Cloud Pak for Integration) or you can leverage the IBM-managed versions that IBM provides via IBM Cloud.
More information is available:
https://www.ibm.com/cloud/api-connect
https://www.ibm.com/cloud/app-connect
https://www.ibm.com/cloud/cloud-pak-for-integration
Can FHIR .NET API be used to create resources from USCORE / CARINBB profiles?
I know we cannot use partial class concept unless we fork the code and change it, So, How to create profile objects within .NET API so I can post to FHIR Server?
US Core and Carin BB simply constrain the allowed values for certain resources. The resources themselves are the same. So a US Core Lab Observation is still an Observation - and can be created using the .NET API like any other Observation. There's no mechanism in the .NET API that exposes a US Core or Carin-BB specific API that automatically enforces those constraints. However, you should be able to use the .NET API to validate an instance against one the profiles from those IGs so long as you load the IG package into memory.
I was wondering if any of the major cloud providers (AWS, Azure, Google) exposed their SLAs for virtual machines via a RESTful API.
Basically, I am looking for the information available on these pages:
https://aws.amazon.com/compute/sla/
https://cloud.google.com/compute/sla
https://azure.microsoft.com/en-gb/support/legal/sla/virtual-machines/v1_8/
Does anyone know if this information is exposed by any of these providers via a RESTful API?
Many thanks.
I was informed by Azure Support that this service is not provided by them.
On Google Cloud Platform there is no way to check the information that you are asking via REST API.
Can you explain your use case and maybe we can find a workaround?
Best regards
I am looking to develop a FHIR based/derived API to support cross system/organisation functions. Primarily for the purposes of audit, and to a lesser degree access control, I would like the initiating system to include** information that describes the origin of the call. This includes:
Source user
Source organisation
Source application (i.e. application name and version)
The first two items can easily be represented with Practitioner however I can't find any resources that could be used to carry source application.
Does anybody know of any resources that could be used for this purpose? Where possible I want to avoid using extensions.
** This is actually being included in an oAuth Client Credentials flow where the calling system obtains a token by providing a system level shared secret and origin. This token is then supplied to the FHIR API method.
Answering my own question
The Device resource covers what I need:
http://hl7.org/fhir/device.html