ServD 1.0 FTF Avatar
  1. OMG Issue

SERVD — Unable to identify location of RetrieveDetailsURL for pending changes

  • Key: SERVD-10
  • Legacy Issue Number: 18654
  • Status: closed  
  • Source: HealthConnex ( Brian Postlethwaite)
  • Summary:

    When retrieving the list of changes that are available the results do not indicate the location of a retrieve details service that can provide the complete object, and also missing is the "parent" object which can be used to locate the entity pending the change (specifically where there is no Retrieve method for the entity, such as an address or contact point, as they are in the context of a provider, or organization)

  • Reported: ServD 1.0b1 — Fri, 12 Apr 2013 04:00 GMT
  • Disposition: Resolved — ServD 1.0
  • Disposition Summary:

    The RecordRequiringApproval Data structure is to be extended to include 2 new properties, one for the RetrieveDetailsURL, and another for the Parent Records index.
    To make this change more apparent the diagram in section 8.2.6 on page 29 on the Reject Change Workflow is modified to separate the MaintainableServD Core into the 2 interfaces to show which interface is required to be called

  • Updated: Sat, 7 Mar 2015 00:17 GMT