SubjectID is the person identifier in the name-service (directory service) associated with the repository (e.g. login name). Thogh the SubjectID is a SecurityPrincipalType (which CAN be a UID/GUID) - the server should always make a best effort to return the current username assocated with that ID. PersonName is the person's formal - traditional - pre-electronic era - name. HRAlias is a 'tag' - you can use to identify differnt HRs for a given person. Like 'public' and 'private', or 'emergency phr'. The tag means nothing to HealthFrameWorks (except that some user interfaces may display the alias). Many of these flags about supported features are - in a sense unnecessary. In many cases, they tell what methods are supported. The caller COULD just call to see. But for methods that are destructive, thats not a good strategy. Thats the reason behind much of the list of features which can be queried. o SetPassword - tells if the SetUserPassword web-method is supported o ServersideSnapshots_Automatic - tells if snapshots are automatically created as the user makes changes, so that you can use the GetSnapshots () interface to view old versions of a file. o ServersideSnapshots_Manual - tells if snapshots can be manually created (server-side) with the ForceSnapshotNow web-method. Note - they can always be created client-side via the HRDB_V1::Export () web-method. o SecurityPolicy - tells if you can call GetSecurityPolciy/SetSecurityPolicy - to control access to HRs. Note - this says if the feature is supported - and is independent of user-login ID. Even if supproted, attempts may fail due to inadequate access privileges o ReadOnlyRepository - tells that the repository is read-only (for example a collection of demo files) Some repositories may have extended information or services users may want to access via a web browser. These include things like accessing account information (e.g. billing), or resetting a password. These features are all provided through a regular web browser interface - disconnected from the web-service interface. o AboutRepository - Top level description of repository, often with links to privacy, or terms of services pages o PasswordResetOrLostUID - Users forget usernames and passwords all the time. This will generally be the link invoked from the HF 'login' dialog - to walk the user though the process of recovering their username/password. o AccountInformation - This page is the per-user-account setup/configuration page. The details of what is displayed here will depend on the details of the service storing the medical recods. Note - any or none of these URLs may be present for a given repository. And - they are all free form web pages, to be viewed by a user in a separate web browser. This function is used to provide a uniform 'interface' to interface versioning. You can call this web method on most HealthFrameWorks web interfaces to request a particular interface. Generally - the 'ID' passed is the same as the namespace used to define the WSDL defining th einterface. The object is often optional, but whether its needed depends on context. Since different interfaces maybe supported on different ports or even hosts, this method returns a URL. Call this method before calling other methods that require may require authentication, to force the authentication process to go forward. It CAN return an alternate URL for use in the remainder of authenticated transactions (perhaps containing authentication information). Returns a list of supported authentication schemes. This can be called without first connecting. Return a description of the target repository. This can be called without first connecting. Returns the set of features supported by this repository. This can be called without first connecting. If AUTH information is provided - it will be ignored. Some feautres - though supported by the interface, may not be supported for particular users with particular authentication information. Find the conventional web browser web-page to access the service given by webConfigPage for the user given by userName. This function generally requires no authentication to use, so the url returned - will be to a web-browser resource which itself will impose its own security checking. This function may return "" for features not supported. Sets the HRAlias (aka tag name) assocated with the given HR. See the documentation for HRDescription for more details. Sets the Subject assocated with the given HR. See the documentation for HRDescription for more details. Returns all health records (which are listable by the connected user). Returns all health records whose name/subject matches the argument match string (returns all which are listable by the connected user). Returns all health records for the given subject (returns all which are listable by the connected user). Returns several values, including name, user-image, etc - for a given health record (HR). Open the health record (named by hrid). If successful, this returns a URL where you connect to another interface. Use IInterface mechanism to see which (currently http://www.RecordsForLiving.com/Schemas/2008-10/HealthFrameWorks/PHRExchange_V1/ and http://www.RecordsForLiving.com/Schemas/2009-04/HealthFrameWorks/IHRDB_V1/ supported). Creates a new medical record in the repository and returns the HRID. The subject of the HR is optional, but if omitted, it defaults to the current user connected. The hrAlias is also optional. Delete the given HR - named by hrid - if present. Returns file size/date/etc information associated with a given health record. Takes the given BLOB of data and hrid, and restores the state of the given health record to that given in the argument blob. Set the given users password. Note - this will likely require a SOAP AUTH header containing the current user password information. And which user is being updated comes from the SOAP auth header. If your repository is configured to store snapshots (perhaps as part of an audit trail), this web method will return the list of all such snapshots. Snapshots are named by date/time (as well as HRID). Returns a read-only BLOB of data which constitutes a time-based snapshot of the given health record. See the GetSnapshots () API to see what snapshots are available. If the repository supprots the ServersideSnapshots_Manual feature, you can call this to force a snapshot to be taken of the current state of the health record given by HRID. Like RestoreBackup - but the source of the restore is a saved snapshot on the server - with the given HRID Return the SecurityPolicy associated with a given HR Sets SecurityPolicy associated with a given HR