FHIR Chat · Library files on missing JSON element names on AHRQ · cql

Stream: cql

Topic: Library files on missing JSON element names on AHRQ

Alex Goel (Jul 08 2021 at 19:25):

Hi, I have a question about a number of files I've looked at a few different examples on Libraries on the AHRQ site and the files seem to be missing the element names. I'm trying to build PlanDefinitions from them. However the IG tooling says the files do not seem to be FHIR since they are missing all of the element names. Example files: https://cds.ahrq.gov/cdsconnect/artifact/factors-consider-managing-chronic-pain-pain-management-summary

{
   "library" : {
      "identifier" : {
         "id" : "FHIRHelpers",
         "version" : "4.0.1"
      },
      "schemaIdentifier" : {
         "id" : "urn:hl7-org:elm",
         "version" : "r1"
      },
      "usings" : {
         "def" : [ {
            "localIdentifier" : "System",
            "uri" : "urn:hl7-org:elm-types:r1"
         }, {
            "localIdentifier" : "FHIR",
            "uri" : "http://hl7.org/fhir",

E.g. in this example it should be "resourceType": "Library",

Is there some kind of header file or something that adds the element names?
@Paul Puscas @Christa Wan

JP (Jul 08 2021 at 20:07):

Those are ELM libraries (i.e. executable files like a Java library or a C++ library) and not FHIR Resources. ELM libraries and typically embedded inside of FHIR Libraries when deployed to a FHIR server.

Alex Goel (Jul 08 2021 at 20:10):

Oh I see! So I'd have to generate the FHIR libraries separately

Chris Moesel (Jul 12 2021 at 18:35):

Right. Many of the artifacts on CDS Connect publish only the CQL libraries (and not the FHIR Clinical Reasoning / CPG resources). There are a few that also publish the PlanDefinition and such, but many do not.

Alex Goel (Jul 13 2021 at 14:53):

@Chris Moesel Are these PlanDefinitions automatically generated from the CQL? I see that the AUDIT Logic files include a PlanDefinition https://cds.ahrq.gov/cdsconnect/artifact/alcohol-screening-using-usaudit-alcohol-use-disorders-identification-test This makes it difficult to consistently implement these files if there is a different set of files that come down and we can't generate the PlanDefinitions from the CQL ourselves

Chris Moesel (Jul 13 2021 at 15:26):

@Alex Goel - I believe that particular artifact was developed by @David Winters and his team on behalf of CDC. As CDS Connect is a repository containing artifacts from a variety of sources and authors, there will be variation in the content and structure of download packages. Some may contain PlanDefinitions, others may not. How those PlanDefinitions came to be (hand-authored, generated, some hybrid of those) may also vary. I think the particular ones you are referring to were hand-authored, but @David Winters should be able to confirm.

Alex Goel (Jul 13 2021 at 15:41):

Are there any efforts to standardize what is uploaded or at least flag what has what kinds of resources? Everything just says "Logic File"

David Winters (Jul 13 2021 at 15:46):

Yep, @Chris Moesel is correct that those PlanDefinitions are hand-crafted. There really isn't much to them, aside from the metadata. Basically a top-level action with include/exclusion criteria, with an action to present the Questionnaire. Happy to answer questions you might have about those files. Would also be interested to hear more about how you're using them.

Chris Moesel (Jul 13 2021 at 16:41):

@Alex Goel -- CDS Connect is pretty open regarding what types of artifacts it allows (not just CQL), so we felt it was best to have a pretty light-handed approach to logic files and what could be uploaded. That said, we are open to ideas about how this can be improved, especially for consumers of the repository. Perhaps if we understood your use case better we could consider additional approaches to better suit you. Are you aiming to programatically consume resources from the repository?

Alex Goel (Jul 13 2021 at 17:29):

I think if there was at least a list of what Logic files were included in the zip that would be very helpful, as well as a search and sort features so that we could find the ones that contain PlanDefinitions for example or the ones which are just CQL

Ideally we'd like to programmatically consume the resources, but right now it's very manual

Chris Moesel (Jul 13 2021 at 19:14):

OK. Understood. Being able to search for artifacts by the standards they use makes sense. @Matt Coarr / @Dylan Mahalingam -- we should put this in the backlog (if it isn't already there).

Alex Goel (Jul 13 2021 at 19:23):

Amazing! Thank you!

Last updated: Apr 12 2022 at 19:14 UTC