Stream: implementers
Topic: Payer Extract
Bryn Rhodes (Sep 17 2016 at 05:56):
Hi All, we'll be using this topic for the Payer Extract track.
Bryn Rhodes (Sep 17 2016 at 12:53):
Here's a document I've put together with all the links you'll need for today's track:
Bryn Rhodes (Sep 17 2016 at 12:53):
https://docs.google.com/document/d/1ccl0NhOXmuJtTux8IK5RNLRB2U7K-A5IUzqZnVUyX3s/edit?usp=sharing
Kanwarpreet Sethi (Sep 17 2016 at 13:34):
@Bryn Rhodes do we have the HSPC test server active for today, or just sticking with HAPI and Aegis servers?
Bryn Rhodes (Sep 17 2016 at 13:53):
We are getting an HSPC up, there's an issue with external references in the test data loads that we're working through now.
Bryn Rhodes (Sep 17 2016 at 14:09):
Here's a patient for the COL measure:
Bryn Rhodes (Sep 17 2016 at 14:09):
http://fhirtest.uhn.ca/baseDstu3/Patient/Patient-12214
Bryn Rhodes (Sep 17 2016 at 14:12):
The CBP patients are 12217, 18, and 19
Travis Cummings (Sep 17 2016 at 14:44):
http://open-api2.hspconsortium.org/payerextract/data
Patrick Haren (Sep 17 2016 at 15:46):
trying cbp and getting a failure response...
Patrick Haren (Sep 17 2016 at 15:46):
http://measure.eval.kanvix.com/Measure/cbp/$evaluate-measure?patient=Patient-12219
Bryn Rhodes (Sep 17 2016 at 15:46):
Here's the payer IG
Bryn Rhodes (Sep 17 2016 at 15:46):
On the CBP, I'll take a look.
Bryn Rhodes (Sep 17 2016 at 16:34):
Here's the value set for Colorectal Cancer that we're using: 2.16.840.1.113883.3.464.1003.108.12.1001
Bryn Rhodes (Sep 17 2016 at 16:41):
Snomed-ct url: http://snomed.info/sct
Bryn Rhodes (Sep 17 2016 at 18:22):
https://github.com/DBCG/cql_measure_processor/blob/a8a7d3744bf6448bdaf6a611b2e80593548fa9d6/pom.xml
Bryn Rhodes (Sep 17 2016 at 20:05):
http://fhir.ext.apelon.com/dtsserverws/fhir/ValueSet/2.16.840.1.113883.3.526.2.1045
Bryn Rhodes (Sep 17 2016 at 20:06):
This is returning the 8462-4 code twice?
Bryn Rhodes (Sep 17 2016 at 20:45):
Okay, the service has been updated, it's now using the dedicated HSPC instance as it's data source, and it's using the Apelon terminology server.
Bryn Rhodes (Sep 17 2016 at 20:47):
Bryn Rhodes (Sep 17 2016 at 20:47):
Bryn Rhodes (Sep 18 2016 at 13:16):
So, in trying to load the value sets into the source servers, I've found that the ValueSet resource returned by the $expand actually fails validation. It is missing the "status" element (should probably be "active") and the "expansion.identifier" element.
Bryn Rhodes (Sep 18 2016 at 13:16):
I'm having to set these when I load them into the target systems, just FYI.
Bryn Rhodes (Sep 18 2016 at 13:25):
@Grahame Grieve I'm trying to run this scenario by loading the value sets into your server, but I'm getting an error from this:
Bryn Rhodes (Sep 18 2016 at 13:25):
Bryn Rhodes (Sep 18 2016 at 13:25):
I thought it was that I didn't have the valueset loaded, but I've verified it's there:
Bryn Rhodes (Sep 18 2016 at 13:25):
http://fhir3.healthintersections.com.au/open/ValueSet/2.16.840.1.113883.3.464.1003.108.12.1020
Bryn Rhodes (Sep 18 2016 at 13:41):
Bryn Rhodes (Sep 18 2016 at 13:41):
Here's another one that's taking 40 seconds:
Grahame Grieve (Sep 18 2016 at 14:01):
no status? but there's a status on the value set being expanded?
Grahame Grieve (Sep 18 2016 at 14:04):
Grahame Grieve (Sep 18 2016 at 14:04):
you have a typo - should be http://fhir3.healthintersections.com.au/open/Observation?subject=Patient/12214&code%3Ain=2.16.840.1.113883.3.464.1003.108.12.1020
Patrick Haren (Sep 18 2016 at 14:37):
To test batch/bulk requests to the payer extract server, does anyone have a specification of the POST message body/resource, or is it a param list?
Kanwarpreet Sethi (Sep 18 2016 at 14:38):
@Patrick Haren I dont think the server (measure engine) is able to do bulk patients right now. I tried it yesterday and got a bad request message
Bryn Rhodes (Sep 19 2016 at 12:50):
@Grahame Grieve It's not a typo, the patient's id is 'Patient-12214'. If I switch it to:
Bryn Rhodes (Sep 19 2016 at 12:50):
Bryn Rhodes (Sep 19 2016 at 12:50):
Then it works, but the spec says an id without the path is valid.
Bryn Rhodes (Sep 19 2016 at 12:51):
But maybe in the case that the subject can be multiple types, the path is required?
Grahame Grieve (Sep 19 2016 at 13:02):
yes the type must be provided. we changed that
Bryn Rhodes (Sep 19 2016 at 18:51):
Okay, fixed that and updated the measure processing component. Both measures are functional for the test data.
Last updated: Apr 12 2022 at 19:14 UTC
