Document Registry: Difference between revisions
No edit summary |
|||
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
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. | |||
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== | ==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]] (XDS)=== | |||
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, | |||
This Profile depends on the actor to | * 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 perform the same functions as for XDS above. | |||
==See Also== | ==See Also== | ||
This actor is often grouped with: [[Document Repository]], [[Secure Node]] and [[Time Client]] | |||
This actor is often grouped with: [[Secure Node]] | |||
This page is based on the [[Actor Template]] | This page is based on the [[Actor Template]] | ||
Latest revision as of 15:46, 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 (XDS)
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 perform the same functions as for XDS above.
See Also
This actor is often grouped with: Document Repository, Secure Node and Time Client
This page is based on the Actor Template