Stream: implementers
Topic: FHIR Testing
RP (Jul 19 2018 at 17:48):
For TestScriptOperationCode what value should be used for an operation of patching a resource with id currently we have update mapped to the TestScriptOperationCode:update ? What is the way to differentiate between an update with Http PATCH vs PUT?
Richard Ettema (Jul 19 2018 at 17:57):
The FHIR STU3 TestScript definition of these codes is missing the 'patch' code. This has been corrected for the R4 release and can be seen in the latest FHIR CI build specification site.
RP (Jul 19 2018 at 17:58):
Okay thank you!
Richard Ettema (Jul 19 2018 at 18:00):
The binding of the TestScriptOperationCode valueset is Extensible (in both STU3 and R4). So, you can put in the 'patch' code as long as you use a different code system. For example,
<type>
<system value="http://hl7.org/fhir/testscript-operation-codes-extended"/>
<code value="patch"/>
</type>
Richard Ettema (Jul 19 2018 at 18:02):
Remember in R4 you will go back to the defined code system "http://hl7.org/fhir/testscript-operation-codes".
RP (Jul 19 2018 at 18:06):
Got it thanks!
Acl (Jul 19 2018 at 23:19):
I'm trying to post an HTTP message with some headers:
test:
- name: Transform
action:
- operation:
label: Update by Patient ID
type:
system: http://hl7.org/fhir/testscript-operation-codes
code: update
requestHeader:
field: "Content-Type"
value: "application/json"
I came up with the above structure as per the examples. (type and requestHeader are siblings). The above hierarchy is not accepted for requestHeader. Let me know if i'm missing something. Screen-Shot-2018-07-19-at-4.22.35-PM.png
Last updated: Apr 12 2022 at 19:14 UTC
