The ReferralNet messaging services provides the ability to transform documents within a Registry Package and can be invoked by either the sending actor prior or the recipient actor. Transformations can be built and associated to specific message types which are denoted by the classification mechanism. Transformations are built and deployed based on user requirements and help facilitate interoperability between sender and receiver, for example, the sending actor may send documents that the recipient actor is not able to consume without some degree of augmentation.

The sending actor may well supply a CDA document when the recipient actor is only able to parse a v2.3.1 HL7 message for the short to medium term, based on the classification of the incoming registry package or documents within the package, a transformation could be located and applied to the payload(s), returning the supported format of the recipient. This will provision the ability for organisations to gain re-use of their tried and tested message specifications until ready for change. As the transformations are available to other ReferralNet subscribers, they too can leverage the re-use these transformations facilitate.

The actual transformation process is initiated through invocation of the TransformDocumentSet operation, supplying the specific transformation identifier (transformUID).

Note Transformations are entirely optional, transport security (SSL) is enforced at all times with no data ever persisted within the ReferralNet messaging service infrastructure. Message encryption is not required as the recipient is itself the invoking process.

Sample Request
Sample Response
<ns6:RetrieveTransformsResponse xmlns:ns6="urn:global-health:referralnet">
   <ns3:RegistryResponse status="Success" xmlns:ns3="urn:oasis:names:tc:ebxml-regrep:xsd:rs:3.0"/>
      <ns6:description>Modifies a HL7 message to accommodate MD2 and MD3 parsing requirements</ns6:description>
dev/refnet_retrieve_transforms.txt · Last modified: 2009/05/18 14:41 by timc