FindMember

The FindMember method is used to locate other valid members of the ReferralNet network only, it supports the search criteria of user id, name and email address. It supports three types of search criteria, by name which harnesses the power of the Natural / Organic search, by email address and by SERIAL for matching against a certificate serial number and issuer.

The method will not return members that have been disabled or have expired subscriptions.

<FindRequestType xmlns="urn:global-health:referralnet">
   <Filter>NAME</Filter>
   <Value>laure</Value>
</FindRequestType>
<ns6:FindMemberResponse xmlns:ns6="urn:global-health:referralnet">
   <ns3:RegistryResponse status="Success" xmlns:ns3="urn:oasis:names:tc:ebxml-regrep:xsd:rs:3.0"></ns3:RegistryResponse>
   <ns6:Member firstName="Lauren" lastName="Harding" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="ns6:ActorType">
      <ns6:id>charliemottram</ns6:id>
      <ns6:Title>Dr</ns6:Title>
      <ns6:Organisation>Global Health</ns6:Organisation>
   </ns6:Member>
   <ns6:Member firstName="Laurent" lastName="Ramelet" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="ns6:ActorType">
      <ns6:id>LaurentR</ns6:id>
      <ns6:Title>Mr</ns6:Title>
   </ns6:Member>
</ns6:FindMemberResponse>

The below example shows the strength and flexibility of a natural search.

<FindRequestType xmlns="urn:global-health:referralnet">
   <Filter>NAME</Filter>
   <Value>global</Value>
</FindRequestType>
<ns6:FindMemberResponse xmlns:ns6="urn:global-health:referralnet">
   <ns3:RegistryResponse status="Success" xmlns:ns3="urn:oasis:names:tc:ebxml-regrep:xsd:rs:3.0"></ns3:RegistryResponse>
   <ns6:Member firstName="Mathew" lastName="Cherian" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="ns6:ActorType">
      <ns6:id>MathewCherian</ns6:id>
      <ns6:Title>Mr</ns6:Title>
      <ns6:Organisation>Global Health Ltd</ns6:Organisation>
   </ns6:Member>
   <ns6:Member firstName="Tim" lastName="Clarke" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="ns6:ActorType">
      <ns6:id>timc</ns6:id>
      <ns6:Title>Mr</ns6:Title>
      <ns6:Organisation>Global Health Limited</ns6:Organisation>
   </ns6:Member>
   <ns6:Member firstName="Vikas" lastName="David" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="ns6:ActorType">
      <ns6:id>vikasd</ns6:id>
      <ns6:Title>Mr</ns6:Title>
      <ns6:Organisation>Global Health</ns6:Organisation>
   </ns6:Member>
   <ns6:Member firstName="David" lastName="Grinberg" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="ns6:ActorType">
      <ns6:id>davidlg</ns6:id>
      <ns6:Title>Mr</ns6:Title>
      <ns6:Organisation>Global Health</ns6:Organisation>
   </ns6:Member>
   <ns6:Member firstName="Lauren" lastName="Harding" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="ns6:ActorType">
      <ns6:id>charliemottram</ns6:id>
      <ns6:Title>Dr</ns6:Title>
      <ns6:Organisation>Global Health</ns6:Organisation>
   </ns6:Member>
   <ns6:Member firstName="Byron" lastName="Jones" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="ns6:ActorType">
      <ns6:id>byron jones</ns6:id>
      <ns6:Title>Mr</ns6:Title>
      <ns6:Organisation>Global Health</ns6:Organisation>
   </ns6:Member>
   <ns6:Member firstName="Ryder" lastName="Manson" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="ns6:ActorType">
      <ns6:id>ryder</ns6:id>
      <ns6:Title>Mr</ns6:Title>
      <ns6:Organisation>Global Health</ns6:Organisation>
   </ns6:Member>
</ns6:FindMemberResponse>

The below example shows the request and response of a member search using an email address as the filter context, if a location certificate is in use at a particular location but split across several member accounts then you will receive more than one member element in the response list.

Note: This search uses supports partial email addresses, so a criteria of clarke, .net.au and bigpond.com are valid.

<FindRequestType xmlns="urn:global-health:referralnet">
   <Filter>EMAIL</Filter>
   <Value>byron.jones@global-health.com</Value>
</FindRequestType>
<ns6:FindMemberResponse xmlns:ns6="urn:global-health:referralnet">
   <ns3:RegistryResponse status="Success" xmlns:ns3="urn:oasis:names:tc:ebxml-regrep:xsd:rs:3.0"></ns3:RegistryResponse>
   <ns6:Member firstName="Byron" lastName="Jones" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="ns6:ActorType">
      <ns6:id>byron jones</ns6:id>
      <ns6:Title>Mr</ns6:Title>
      <ns6:Organisation>Global Health</ns6:Organisation>
   </ns6:Member>
</ns6:FindMemberResponse>

The below example shows the request a member search using certificate serial and issuer as the filter context. This is the preferred method of finding users that have a particular certificate. Note that there is no assumption regarding who the certificate issuer is.

The serial number must be in decimal format. The matching certificate is shown below.

This only returns a match if the user has a messaging subscription.

<FindRequestType xmlns="urn:global-health:referralnet">
   <Filter>SERIAL</Filter>
   <Value>387802$CN=Test Medicare Australia Organisation Certification Authority,OU=Medicare Australia,O=GOV,C=AU</Value>
</FindRequestType>

 
dev/find_member.txt · Last modified: 2017/03/31 00:28 by damong