Difference between revisions of "OHF Bridge Documentation"

Revision as of 17:59, 8 November 2006

This page will try to supply missing documentation problems occurring due to the frequent updates and new requirements we receive from the IHE Connectathon 2007 tests.

Changes in Beta 3 Web services API

• Changing pidType to patientIdType in order to avoid HL7 namespace conflicts.
• Adding a "is PHAD" boolean to the RHIO config
• Changed the names of the send document operations and added one that suits the IHE Connectathon 2007 most (see API clarifications)
• In the XDSDocType, changed the name of EncodedDocument to Base64EncodedDocument
• In DateTimeRangeType changes attribute to attributeName (make it more clear)
• In FindDocumentsByPatientId using PatientIdType for the patient type instead of a string

API Clarification

Sending documents

In beta 3 we've changed the name of the method to clarify the document submission process and make testing for Connectathon 2007 possible. These are the only submission options for Connectathon 2007 testing.

• SubmitDocument (use for Connectathon Test 11746)
  • This service accepts a CDA R2 formatted document and other necessary XDS Metadata needed for submission. This service will automatically extract XDS Metadata from this document and supplement the metadata with values from a DocumentSubmissionMetadataType object. An example of this object will be posted soon.

• ReplaceDocument (use for Connectathon Test 11748)
  • This service accepts a CDA R2 formatted document and other necessary XDS Metadata needed for submission. This service will automatically extract XDS Metadata from this document and supplement the metadata with values from a DocumentSubmissionMetadataType object, including the UUID of the parent document in the XDS registry to be replaced. An example of this object will be posted soon.

Bridge users must provide the patientID and their sourceID (an OID) along with the codesthey feel best describe the submission they are executing. These codes can be fixed, in many cases, based on the kind of application you own. Choices of codes can be found here. A parent document UUID must be provided in the case of document replacement.

General comment regarding the "DecodedDocument" field. Please ignore it. We had placed it there to overcome a problem we had with SOAP object translation and we intend to remove it soon.

Searching for Documents

• DateTimeRangeType is used for searching a document with date constraints.
  • There might be more then one DateTimeRangeType in a search. There are five types of DateTimeRangeType distinguished by their AttributeName:
    • creationTime
    • serviceStartTime
    • serviceStopTime
    • submissionTime
    • lastUpdateTime
  • Time/date (To and From) must follow this format: YYYY[MM[DD]]