Stream: implementers
Topic: Patient Track
Oleksandr (Alex) Ostrynskyy (Sep 17 2016 at 16:03):
Starting a stream for the patient track
Oleksandr (Alex) Ostrynskyy (Sep 17 2016 at 16:04):
My public ip is 162.129.250.13
Sorin Voicu (Sep 17 2016 at 16:04):
https://fhirsandbox1.tsysinteropsvcs.net:8100/site/123/
Sorin Voicu (Sep 17 2016 at 16:12):
Alex, we are able to reach https://fhirsandbox1.tsysinteropsvcs.net:8100/site/123/ from multiple networks - T-Mobile, Sprint, AT&T.
Nathan George (Sep 17 2016 at 16:16):
our server is at http://192.168.16.120/imat/fhir (STU3)
David Hay (Sep 17 2016 at 16:20):
Nathan: that url is unreachable unfortunately...
David Hay (Sep 17 2016 at 16:22):
Alex: what's the url for your conformance resource?
Oleksandr (Alex) Ostrynskyy (Sep 17 2016 at 16:24):
JHH server is http://192.168.16.172:57772/csp/healthshare/jhhs/fhir
Oleksandr (Alex) Ostrynskyy (Sep 17 2016 at 16:25):
http://192.168.16.172:57772/csp/healthshare/jhhs/fhir/metadata
Nathan George (Sep 17 2016 at 16:25):
http://192.168.16.120/imat/fhir/metadata is where conformance resource should be located
Sorin Voicu (Sep 17 2016 at 16:28):
That looks like an IP internal to a network
David Hay (Sep 17 2016 at 16:31):
indeed...
Nathan George (Sep 17 2016 at 16:33):
yes, its only available on the HL7SEP2016 network at the Connectathon (for now)
David Hay (Sep 17 2016 at 17:34):
I get an 'unreachable' error...
Oleksandr (Alex) Ostrynskyy (Sep 17 2016 at 17:35):
Nathan, could you please check your server. I just sent a FHIR request but getting ""This is the base URL of FHIR server. Unable to handle this request, as it does not contain a resource type or operation name." Wondering what's wrong with the request?
David Hay (Sep 17 2016 at 17:52):
{
"resourceType": "OperationOutcome",
"issue": [
{
"severity": "error",
"code": "processing",
"diagnostics": "Unable to get search content count"
}
]
}
Sorin Voicu (Sep 17 2016 at 17:57):
@David Hay For the T-System server, CORS is now enabled if you'd like to try it again
Nathan George (Sep 17 2016 at 18:59):
@David Hay The imat/fhir server should return the correct 0 hits found instead of the error message now
Last updated: Apr 12 2022 at 19:14 UTC
