Stream: implementers
Topic: Montreal
Grahame Grieve (Apr 26 2016 at 17:46):
I have just upgraded my server (http://fhir3.healthintersections.com.au). This upgrade:
- fixes lots of invariant expressions (thx to Richard Ettema for help on this)
- fixes bugs in the patient compartment + adds support for the other compartments
- fixes reported bugs
- makes the latest definitions for montreal available (if you don't have svn - see http://fhir3.healthintersections.com.au/index.html)
Igor Sirkovich (Apr 26 2016 at 19:07):
Grahame, the yellow box in the top of the http://fhir3.healthintersections.com.au/index.html says "This is the Current officially released version of FHIR, which is DSTU 2". I believe this should be aligned with http://www.hl7.org/fhir/2016May: "This is a pre-release of a future version of FHIR (expected to be STU 3) for the 2016 May Montreal Connectathon and the CQF on FHIR Ballot. The current version is DSTU 2."
Igor Sirkovich (Apr 26 2016 at 19:08):
BTW, http://fhir2.healthintersections.com.au/index.html says "This is the Continuous Integration Build of FHIR (will be incorrect/inconsistent at times)"
Grahame Grieve (Apr 26 2016 at 19:09):
yeah, both of those statements on my servers are wrong. just goes to show that the way i've built those sites is a bit haphazard
Grahame Grieve (Apr 26 2016 at 19:09):
I'll see if I can fix that
Eric Haas (May 01 2016 at 13:05):
Where is the schema file for Montreal? Should I use the current build?
Brian Postlethwaite (May 01 2016 at 13:25):
http://hl7.org/fhir/2016May/index.html
Eric Haas (May 01 2016 at 13:35):
I tried a PUT to http://fhir3.healthintersections.com.au/open/Patient which returned an access violation. works on http://fhir2.healthintersections.com.au/open/Patient so I suspect is not on my end?
Grahame Grieve (May 01 2016 at 15:58):
what did you put?
Eric Haas (May 01 2016 at 18:23):
http://fhir3.healthintersections.com.au/open/MedicationStatement/dafmed-1001
Eric Haas (May 01 2016 at 18:24):
Access violation at address 0000000001631CCD in module 'FHIRServer.exe'. Write of address 0000000000000018
Josh Mandel (May 01 2016 at 18:41):
Also clicking on Eric's link, I can't help noticing
Server Home. | FHIR © HL7.org 2011 - 2013. | FHIR Version 1.4.0
(Should probably extend to 2016.)
Grahame Grieve (May 01 2016 at 19:10):
Eric this hasn't brought me clarity. You PUT a Medication statement to the Patient end-point?
Eric Haas (May 01 2016 at 19:20):
Tried several different resources seems to be operator errors so far - I was getting lazy since the DSTU2 version didn't require Accept and Content-types in header I skipped them.
Eric Haas (May 01 2016 at 19:20):
when I add them in the PUTs work just fine
Grahame Grieve (May 01 2016 at 19:22):
oh? have i changed behaviour on this? That's probably a side effect of adding RDF and JSON-LD support
Eric Haas (May 01 2016 at 19:24):
Its not clear to me the difference. in DSTU2 the resources load without headers but errors when add headers.. in STU3 the opposite is true. I'm also trying to load condition but getting this error....
Eric Haas (May 01 2016 at 19:24):
Error in profile for Condition.onsetDateTime multiple types defined in slice discriminator
Grahame Grieve (May 01 2016 at 19:25):
load --> you mean "put" them?
Eric Haas (May 01 2016 at 19:25):
Is that a profile error and not an instance error. i.e. no matter what - it will always error
Eric Haas (May 01 2016 at 19:25):
yes PUT
Grahame Grieve (May 01 2016 at 19:26):
so you put XML(?) without a content-type header, and it works on fhir2.healthintersections.com.au? but not on fhir3? what are you using for a header?
Eric Haas (May 01 2016 at 19:27):
PUT http://fhir2.healthintersections.com.au/open/MedicationStatement/dafmed-1001 HTTP/1.1
User-Agent: Fiddler
Host: fhir2.healthintersections.com.au
Content-Length: 1167
Eric Haas (May 01 2016 at 19:29):
PUT http://fhir3.healthintersections.com.au/open/MedicationStatement/dafmed-1001 HTTP/1.1
User-Agent: Fiddler
Host: fhir3.healthintersections.com.au
Content-Length: 1167
Content-type: application/xml+fhir
Accept: application/xml+fhir
Eric Haas (May 01 2016 at 19:30):
These PUTs return a 200, The opposite returns errros
Grahame Grieve (May 01 2016 at 19:37):
the error on fhir2 indicates I have real problems with the older version; my forked version of the build is not escaping or unescaping something properly, but it shouldn't work without that. weird
Eric Haas (May 01 2016 at 19:44):
Re profile error - likely a DAF Tracker already will check. but fixed by removing the element for now.
Grahame Grieve (May 01 2016 at 19:44):
fixed the other error - will put a new server live soon
Grahame Grieve (May 01 2016 at 19:45):
it was because of RDF
Eric Haas (May 01 2016 at 19:47):
Other error?
Grahame Grieve (May 01 2016 at 19:49):
the need for the content-type header
Grahame Grieve (May 01 2016 at 19:49):
which is case sensitive btw
Grahame Grieve (May 01 2016 at 19:49):
Content-Type not Content-type
Eric Haas (May 01 2016 at 19:57):
OK thanks, I made that change. Observation is erroring on PUTs. Fetched a resource from the STU 3 server and when try to PUT get this....
Eric Haas (May 01 2016 at 19:59):
"This does not appear to be a FHIR resource (unknown namespace/name "http://hl7.org/fhir::Observation") at line 0 col 0"
Eric Haas (May 01 2016 at 19:59):
here is resource...
Eric Haas (May 01 2016 at 19:59):
<?xml version="1.0" encoding="UTF-8"?>
<Observation xmlns="http://hl7.org/fhir">
<id value="1"/>...
Eric Haas (May 01 2016 at 20:01):
Interestingly get this error in DSTU2...
Eric Haas (May 01 2016 at 20:01):
"Error in component.where(code = $context.code).empty() at 32: Found . expecting a valid token name"
Eric Haas (May 01 2016 at 20:02):
all the observations I tried to put (~30) in a batch error the same way.
Grahame Grieve (May 01 2016 at 20:05):
hmm works on my local copy
Grahame Grieve (May 01 2016 at 20:13):
I won't be upgrading soon; my connection is too limited to upload the new server
Grahame Grieve (May 01 2016 at 20:13):
I won't be upgrading soon; my connection is too limited to upload the new server
Eric Haas (May 01 2016 at 20:13):
np
Josh Mandel (May 01 2016 at 20:13):
Shouldn't be case sensitive...
http://stackoverflow.com/questions/5258977/are-http-headers-case-sensitive
From RFC 2616 - "Hypertext Transfer Protocol -- HTTP/1.1", Section 4.2, "Message Headers":
Each header field consists of a name followed by a colon (":") and the field value. Field names are case-insensitive.
Grahame Grieve (May 01 2016 at 20:16):
oh? ok. that means that my server is right not to be case sensitive after all
Josh Mandel (May 01 2016 at 20:18):
For header field names, yes.
Michael Lawley (May 05 2016 at 17:00):
@Grahame Grieve your fhir3 server metadata is still listing lookup as being defined on ValueSet rather than CodeSystem (as is defined and implemented) -- "reference" : "http://hl7.org/fhir/OperationDefinition/ValueSet-lookup"
Grahame Grieve (May 05 2016 at 22:01):
where is this reference?
Grahame Grieve (May 05 2016 at 22:28):
Someone just reported a rather savage bug in the generated schemas for the connectathon. Corrected schemas are posted here:
Grahame Grieve (May 05 2016 at 22:28):
Corrected schemas are available at http://www.healthintersections.com.au/fhir-2016-may-schema.zip
Michael Lawley (May 06 2016 at 18:44):
That's a fragment of the json returned from http://fhir3.healthintersections.com.au/open/metadata
"operation" : [
// ...
{
"name" : "lookup",
"definition" : {
"reference" : "http://hl7.org/fhir/OperationDefinition/ValueSet-lookup"
}
},
Josh Mandel (May 06 2016 at 18:47):
$ curl -s 'http://hooks.fhir.me:8081/cms-price-check/$cds-hook-metadata' | json
{
"resourceType": "Parameters",
"parameter": [
{
"name": "name",
"valueString": "CMS Pricing Service"
},
{
"name": "description",
"valueString": "Estimate the price of a prescription based on historical pharmacy dispensing data"
},
{
"name": "activity",
"valueCoding": {
"system": "http://cds-hooks.smarthealthit.org/activity",
"code": "medication-prescribe"
}
},
{
"name": "preFetchTemplate",
"valueString": "Patient/{{Patient.id}}"
}
]
}
Josh Mandel (May 06 2016 at 18:48):
Note that we're working on a simplified spec (to unveil tomorrow, so it can go head-to-head and cause maximum confusion ;-)) that looks like:
$ curl -s 'http://hooks.fhir.me:8082/.well-known/cds-services' | json
{
"services": [
{
"name": "CMS Pricing Service",
"id": "cms-price-check",
"description": "Estimate the price of a prescription based on historical pharmacy dispensing data",
"hook": "medication-prescribe"
},
{
"id": "patient-hello-world",
"name": "Patient hello world",
"description": "Greet patient by name",
"hook": "patient-view",
"prefetch": {
"patientToGreet": "Patient/{{Patient.id}}"
}
}
]
}
Grahame Grieve (May 06 2016 at 20:51):
@Michael Lawley - thanks, fixed
Grahame Grieve (May 06 2016 at 20:52):
@Josh Mandel , tomorrow? really?
Last updated: Apr 12 2022 at 19:14 UTC
