FHIR Chat · Interest in Patch Connectathon Track · implementers

Stream: implementers

Topic: Interest in Patch Connectathon Track

Jenni Syed (Jun 14 2017 at 19:01):

We’re considering creating a PATCH track for the September Connectathon, but wanted to find out how much interest there would be. The proposed track is as follows:

The required scenarios would be like the original track ( http://wiki.hl7.org/index.php?title=201609_PATCH_Connectathon_Track_Proposal ), but we would add some optional scenarios for those interested in the new batch and transaction FHIRPath-based approaches. Essentially (Draft):

http://wiki.hl7.org/index.php?title=201709_PATCH_Connectathon_Track_Proposal

TL/DR:
Required Scenarios:
• Search/Patch Patient using xml or json PATCH
Optional/Bonus Scenarios:
• Patch Patient using FHIRPath
• Version aware Patch for Patient (in whatever forms the server/client supports)
• Batch update using FHIRPath patch
• Transactional update using FHIRPath patch

What we need from you:
• Are you interested? Client and/or Server?
• Are there other scenarios you would be interested in?
(For example: is it ok to limit focus on patient, and any other resource is bonus?)

Grahame Grieve (Jun 14 2017 at 19:29):

I think my server supports all this. But I don't think anyone has been using it...

Christiaan Knaap (Jun 14 2017 at 19:42):

I am interested, but I doubt we will have the time to implement both Subscriptions (other interesting track) and Patch. Can I opt-in later if I think we'll make it after all?

Grahame Grieve (Jun 14 2017 at 19:50):

yes you always can - but that doesn't count against whether we should do this

Richard Kavanagh (Jun 20 2017 at 06:16):

I'd be interested at looking at patch from a client perspective. We were looking at this a little while back but I could not find a server that had implemented it. Maybe it's time to have another look.
I dont think limiting it to Patient is necessarily an issue - our primary use case is around Appointment but that should not matter for the connectathon.

Grahame Grieve (Jun 20 2017 at 11:28):

at least test.fhir.org implements it completely

Richard Ettema (Jun 20 2017 at 14:20):

wildfhir.aegis.net/fhir3-0-1 implements PATCH for XPath and JSONPath

Richard Kavanagh (Jun 21 2017 at 07:20):

Thanks @Grahame Grieve @Richard Ettema I'll take another look

Jenni Syed (Jul 05 2017 at 16:33):

As of now, I don't think we have enough interest in this track to run it and be productive. Unless you know of friends secretly planning to participate... if so, give them a nudge to speak up here

Ewout Kramer (Jul 06 2017 at 15:14):

I know @Christiaan Knaap is thinking about building it into Vonk....maybe the group will slowly grow...

Richard Ettema (Jul 06 2017 at 15:28):

I'll definitely have TestScripts available in Touchstone for anyone interested.

Eric Haas (Aug 29 2017 at 00:39):

@Richard Ettema I got json patch to work. unable to get xml patch to work....

here is the diff:

     <?xml version="1.0" encoding="UTF-8"?>
   <diff>
     <replace sel="Appointment/status/@value">cancelled</replace>
  </diff>

unable to get fhirpath (xml) to work either

here is the params resouce:

<?xml version="1.0" encoding="UTF-8"?>
<Parameters xmlns="http://hl7.org/fhir">
  <parameter>
     <name value="operation"/>
    <part>
      <name value="type"/>
      <valueCode value="replace"/>
   </part>
   <part>
       <name value="path"/>
        <valueString value="status"/>
    </part>
    <part>
       <name value="value"/>
       <valueCode value="cancelled"/>
    </part>
  </parameter>
  </Parameters>

what am I missing?

Grahame Grieve (Aug 29 2017 at 00:47):

namespace, it looks like

Eric Haas (Aug 29 2017 at 01:13):

ty fixed xml path.

for fhir path the error is
<text value="Exception applying XML Patch! unknown operation: parameter"/>

Richard Ettema (Aug 29 2017 at 15:12):

You may want to check your request http header content-type. Remember that the FHIRPath patch sends a Parameters resource so the content mime-type should be 'application/fhir+xml'. The error message indicates the server is attempting to evaluate the request as an XML Patch.

Eric Haas (Aug 29 2017 at 16:09):

@Richard Ettema here is a screenshot of the inputs:

Screen-Shot-2017-08-29-at-9.08.03-AM.png

Eric Haas (Aug 29 2017 at 16:10):

and here is the error message:

Screen-Shot-2017-08-29-at-9.08.17-AM.png

Eric Haas (Aug 29 2017 at 16:10):

I selected fhirpath (xml)

Richard Ettema (Aug 29 2017 at 16:14):

@Eric Haas My apologies. I have not yet implemented the FHIRPath patch operation in my WildFHIR server. (I keep getting side-tracked with other work.) The WildFHIR client interface provides the capability of sending the FHIRPath patch operation so you could select a different server like Grahame's.

Eric Haas (Aug 29 2017 at 16:23):

OK No problem just wanted to make sure you didn't have a bug.

Eric

Jenni Syed (Aug 31 2017 at 15:17):

I wasn't planning on running the patch track this time (not enough people were committed) - but Eric, it looks like you're doing something with it?

Eric Haas (Aug 31 2017 at 15:22):

Was for scheduling not Connectathon.... see https://github.com/argonautproject/scheduling/wiki/Operations#define-handling-of-other-outcomes
Using patch for cancel - so I wanted some examples ( but not sure will work if want to comment at same time - client doesn't know if already existing comments present )

Last updated: Apr 12 2022 at 19:14 UTC