1 / 6

Location Authority - LA

Location Authority - LA. Definition: A cross-community actor which makes available to all authorized communities information about the mapping of some patients to communities which may hold data for that patient.

jerica
Télécharger la présentation

Location Authority - LA

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Location Authority - LA • Definition: A cross-community actor which makes available to all authorized communities information about the mapping of some patients to communities which may hold data for that patient. • May be co-located with a community (internal) or independent of a community (external) • An LA will add and drop patients for which it has data • An LA must ensure that the mapping it maintains is reasonably up-to-date (no more than a few days old) • There may be more than one LA per patient, but it is preferable to have a small number of LA’s per patient. • An LA may be supported as part of a patient home paradigm.

  2. LA internal to community • When an LA is hosted within a community • Use cases to review • New patient in LA • New patient data in a community • Changes in patients inside and outside LA community • Patient no longer supported by LA

  3. QP to all QP to all QP for patient QIL QIL LA within a community Community LA Community Other • Identifies a new patient for which to be a LA – creates a patient identifier to be used in future QIL transactions • Collates results into local table for the patient • Occasional batch query to update local table (U in future) • Update local table if necessary • Respond with a) local ID & demographics b) indicator that will respond to QIL for this patient and patient identifier to use in QIL (could be same as in a) ) • Respond with local table • Patient no longer supported by this LA, delete from table • Respond with “not LA” and perhaps a “look here” identifier

  4. LA external to community • When an LA is not hosted by a community • Requires shared/voluntary identifier • LA contains only identifiers, no demographics • Need LA feeder which creates shared identifier and feeds to LA and other communities • Use cases to review • New patient identifier in LA • New patient data in a community • Changes in patients • Patient identifier no longer supported by LA

  5. QP for patient QIL LA external to any community LA LA Feeding Community Community Other • Create new shared ID • Return local ID & demographics and LA identifier + shared ID Feed shared ID & homeCommunityId • Create new entry in table • Update table • Return table • Update table Feed shared ID & homeCommunityId Merge/link/delete patient ID

  6. Open Issues • Usefulness of both external and internal LA’s and IHE’s support for such in 2009 • Consider names other than LA • LA needs QP to carry initiators homeCommunityId • New transaction needed to feed external LA carrying only patient identifier and homeCommunityId? Or use restricted form of QP?

More Related