Document Registry: Difference between revisions

From IHE Wiki
Jump to navigation Jump to search
Kboone (talk | contribs)
No edit summary
 
Kboone (talk | contribs)
No edit summary
Line 1: Line 1:
''This is a template page.  Click edit, Do Not Save This Page, Copy the current text then go edit your page and paste it in.''
The Document Registry Actor maintains metadata about each registered document in a document entry. This includes a link to the Document in the Repository where it is stored. The Document Registry responds to queries from [[Document Consumer]] actors about documents meeting specific criteria. It also enforces some healthcare specific technical policies at the time of document registration.
 
''<Your page name should simply be Actor-Name Actor with spaces, with capitals, without the acronym. e.g. Order Placer Actor>''
 
The Document Registry Actor maintains metadata about each registered document in a document entry. This includes a link to the Document in the Repository where it is stored. The Document Registry responds to queries from Document Consumer actors about documents meeting specific criteria. It also enforces some healthcare specific technical policies at the time of document registration.
 
__TOC__
 
 
''<Explain the flavor of the tasks and information the actor is responsible for.  This section is profile neutral.>''
 
 
==Responsibilities in Profiles==
==Responsibilities in Profiles==


Line 17: Line 6:
A system that supports an Actor does not have to meet the requirements in any given Profile unless the system claims support of that Profile in the product [[Statements|Integration Statement]].
A system that supports an Actor does not have to meet the requirements in any given Profile unless the system claims support of that Profile in the product [[Statements|Integration Statement]].


===[[Cross Enterprise Document Sharing]]===


===''<Profile 1>''===
This Profile depends on the actor to:
* use patient identifiers provided by a [[Patient Identity Source]] to ensure that XDS Documents metadata registered is associated with a known patient,
* update patient identity in document metadata by tracking identity change operations (e.g. merge)
* index, store and retrieve document metadata,
* recieve and execute queries against the stored document metadata,
* return selected metadata to the [[Document Consumer]]


This Profile depends on the actor to ''<explain in broad terms>''.


 
===[[XDS-I]]===
===''<Profile 2>''===


This Profile depends on the actor to ''<explain in broad terms>''.
This Profile depends on the actor to ''<explain in broad terms>''.
Line 29: Line 22:


==See Also==
==See Also==
 
This actor is often grouped with: [[Document Repository]], [[Secure Node]] and [[Time Client]]
''<Include/explain links to other Actors with similar jobs>''
 
This actor is often grouped with: [[Secure Node]], [[Time Client]]
''<Include links to commonly grouped Actors>''


This page is based on the [[Actor Template]]
This page is based on the [[Actor Template]]

Revision as of 15:40, 28 November 2006

The Document Registry Actor maintains metadata about each registered document in a document entry. This includes a link to the Document in the Repository where it is stored. The Document Registry responds to queries from Document Consumer actors about documents meeting specific criteria. It also enforces some healthcare specific technical policies at the time of document registration.

Responsibilities in Profiles

The responsibilities placed on this actor in the context of each Profile is summarized here. For the actual specifications, refer to the Technical Framework.

A system that supports an Actor does not have to meet the requirements in any given Profile unless the system claims support of that Profile in the product Integration Statement.

Cross Enterprise Document Sharing

This Profile depends on the actor to:

  • use patient identifiers provided by a Patient Identity Source to ensure that XDS Documents metadata registered is associated with a known patient,
  • update patient identity in document metadata by tracking identity change operations (e.g. merge)
  • index, store and retrieve document metadata,
  • recieve and execute queries against the stored document metadata,
  • return selected metadata to the Document Consumer


XDS-I

This Profile depends on the actor to <explain in broad terms>.


See Also

This actor is often grouped with: Document Repository, Secure Node and Time Client

This page is based on the Actor Template