Bills-FHIR-page: Difference between revisions
Created page with "These are my notes on FHIR. As they become mature they will probably migrate to John's page. == FHIR class == March 11, 12 2014 took FHIR class given by HL7 (Floyd taught). The..." |
|||
| Line 4: | Line 4: | ||
March 11, 12 2014 took FHIR class given by HL7 (Floyd taught). The slides from that class are available for download from | March 11, 12 2014 took FHIR class given by HL7 (Floyd taught). The slides from that class are available for download from | ||
[http://gforge.hl7.org/gf/project/fhir/scmsvn/?action=browse&path=%2F%2Acheckout%2A%2Ftrunk%2Fpresentations%2F2014-03%2520Ed%2520Summit%2F201403%2520-%2520Virginia%2520-%2520Hands%2520on%2520FHIR.pptx here] | [http://gforge.hl7.org/gf/project/fhir/scmsvn/?action=browse&path=%2F%2Acheckout%2A%2Ftrunk%2Fpresentations%2F2014-03%2520Ed%2520Summit%2F201403%2520-%2520Virginia%2520-%2520Hands%2520on%2520FHIR.pptx here] | ||
As a summary of the class, I believe that the full semantics of XDS.b can be translated to FHIR. This would mean replacing the ebXML Registry binding with the FHIR binding and replacing the SOAP binding with the combination of FHIR REST and ATOM. I describe it this way because FHIR has its own flavor of REST and ATOM. (a comment, not a criticism). | |||
The class was quite overwhelming in the same way that drinking from a fire hose is overwhelming. | |||
What follows below are my notes from the class. I will continue to add to this page as I discover more things that I learned (see fire hose). | |||
== Transactions a REST == | |||
FHIR has transactions and it has REST. Here I mean REST in the form of direct addressing of individual objects like DocumentEntry and SubmissionSet (XDS terms). | |||
On the direct addressing side, one can submit a single object, say DocumentReference, assigning it a permanent ID or allowing the server to assign the ID. To submit allowing the server to assign the ID you would POST the single DocumentReference object to | |||
<pre> | |||
http://server.com/xds/DocumentEntry | |||
</pre> | |||
where http://server.com/xds define the server and service supporting FHIR (yes, I made them up). | |||
Revision as of 11:06, 12 March 2014
These are my notes on FHIR. As they become mature they will probably migrate to John's page.
FHIR class
March 11, 12 2014 took FHIR class given by HL7 (Floyd taught). The slides from that class are available for download from here
As a summary of the class, I believe that the full semantics of XDS.b can be translated to FHIR. This would mean replacing the ebXML Registry binding with the FHIR binding and replacing the SOAP binding with the combination of FHIR REST and ATOM. I describe it this way because FHIR has its own flavor of REST and ATOM. (a comment, not a criticism).
The class was quite overwhelming in the same way that drinking from a fire hose is overwhelming.
What follows below are my notes from the class. I will continue to add to this page as I discover more things that I learned (see fire hose).
Transactions a REST
FHIR has transactions and it has REST. Here I mean REST in the form of direct addressing of individual objects like DocumentEntry and SubmissionSet (XDS terms).
On the direct addressing side, one can submit a single object, say DocumentReference, assigning it a permanent ID or allowing the server to assign the ID. To submit allowing the server to assign the ID you would POST the single DocumentReference object to
http://server.com/xds/DocumentEntry
where http://server.com/xds define the server and service supporting FHIR (yes, I made them up).