2a. Test in your browser
To look at an API response in your browser, navigate to
https://demo.psm.solutionguidance.com/cms/fhir/Task/1463 (for example). Your browser might ask you if you want to save a file when you navigate
to that page. I'd suggest choosing to open it in the browser, but either will work. The application ID that you found in step 1 forms the last part of the URL, so you can replace "1463" with any of the other IDs. If you choose an ID that doesn't exist on the server, you'll get a "not found" page. Testing the API this way will give you a response that looks like the one in the postscript below.
2b. Test from the command line
If you're not comfortable on the command line that is more than fine. The same information is presented no matter how you look at it.
No real information is stored on our demo server -- all the application and provider data is fake and for testing purposes only.
For more information about the API, please look at
the original pull request, which also links to a discussion in the issue. Respond here with any questions or comments -- I look forward to talking more about this.
Cecilia
P.S. An example of the type of response you will see in your browser:
<Task xmlns="http://hl7.org/fhir">
<contained>
<Practitioner xmlns="http://hl7.org/fhir">
<id value="1489"/>
<identifier>
<system value="http://hl7.org/fhir/sid/us-ssn"/>
<value value="111001111"/>
</identifier>
<identifier>
<system value="http://hl7.org/fhir/sid/us-npi"/>
<value value="0000000006"/>
</identifier>
<name>
<family value="Test"/>
<given value="Cecilia"/>
</name>
</Practitioner>
</contained>
<identifier>
<value value="1463"/>
</identifier>
<status value="requested"/>
<intent value="proposal"/>
<requester>
<agent>
<reference value="#1489"/>
</agent>
</requester>
<input>
<type>
<text value="Provider Type"/>
</type>
<valueString value="Dentist"/>
</input>
</Task>