Hoping someone can help.
I had posted a similar question outside this group a while ago "Errors requesting data from local Ensemble FHIR Repository" but haven't had the chance to follow up on it since. It was suggested I re-post inside this group.
I'm trying to request data from my local FHIR repository using a simple JavaScript client and am getting the following CORS errors . ( It is a standalone client not inside HealthShare without CSP etc. on my localhost ).
Hoping someone can help.
I need to convert a timestamp from the following format (YYYYMMDDhhmmss e.g. 20160105125915) to UTC time in the same format.
I presume I need to convert it to the system format ( like $HOROLOG ) and then use something like ConvertTimeStampToHorolog or perhaps LocalWithZTIMEZONEtoUTC but not sure of the syntax.
Thanks,
The product I'm using is HealthConnect ( this installation HSAP-2017.1.1.111.0.17521-hscore15.03-b8382-win_x64.exe). Do I have access to the Information Exchange Clinical Viewer ? Is there a way to install this and connect it up to my HealthShare FHIR repository?
Hoping someone can help,
I have the "Sample FHIR Production" installed ( as described in the documentation) with the following Components:
Service: HS.Gateway.ECR.SDA3XMLFileService
Processes: HS.FHIR.FromSDA.DTL.Transaction.Process
Operations: HS.FHIR.Repository.Operations
When a patient's data gets updated in my application a new SDA3 message is generated and processed by the FromSDA DTL. The Repository Stores that data as a New patient ( i.e. when I query the Repo they have different IDs "resource":{ "resourceType":"Patient", "id":"4", ) .
Hoping someone can help.
I'm trying to request data from my local FHIR repository using a simple client ( using SMART ). I get the following CORS error in Firebug.
"NetworkError: 406 Not Acceptable - http://localhost:57775/csp/healthshare/fhirserver/fhir/Patient/1"
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://localhost:57775/csp/healthshare/fhirserver/fhir/Patient/1. (Reason: CORS header 'Access-Control-Allow-Origin' missing).
I can request data with no problems using the Chrome RESTClient.