Patient Record Snapshot
1. Proposed Profile: Patient Record Snapshot
- Proposal Editor: Vassil Peytchev
- Profile Editor:
- Date: N/A (Wiki keeps history)
- Version: N/A (Wiki keeps history)
- Domain: PCC
Summary
The PCC technical committee has defined several content profiles describing the data set and format for creating clinical documents for the purposes of interoperability. These summary documents reflect certain workflows (e.g. referrals, hospital discharge). This proposal adds a snapshot content profile, based on the HL7/ASTM CCD implementation guide.
2. The Problem
Many EMR systems continuously update a patient's record, with no set workflow points to create a summary document. When a system from a different enterprise, enabled for cross enterprise document sharing (through XD*), needs to get the current patient summary, there may not be a published referral or discharge summary. In such a case, the ability of the document source to create a Continuity of Care Document will provide the requesting system a way to receive the relevant information.
3. Key Use Case
Patient A presents in the ER with severe chest pains. The patient informs the admitting provider P that his/her primary care provider is at Clinic C. The Document consumer at the ER sends an XDS stored query to the registry in the affinity domain. Since no documents are found, the Document consumer then issues a subscribe request to the registry (a proposed new ITI profile). At the same time the request is also sent to the document source at Clinic C. The current patient information snapshot is then published to the repository and registered in the registry, which pushes the document to the document consumer in the ER.
4. Standards & Systems
CCD IHE ITI XD* profile IHE ITI Publish/Subscribe IHE ITI Async XDS
5. Technical Approach
It is expected the the new proposes ITI profiles for publish/subscribe and for asynchronous XDS will be used in conjunction with this content profile.
Existing actors
- Document Source
- Document Consumer
- Document Registry
- Document Repository
- <ATNA Actors>
New actors
Depends on the technical solution for publish/subscribe
6. Open Issues
<Point out any key issues or design problems. This will be helpful for estimating the amount of work and demonstrates thought has already gone into the candidate profile.>
An on-demand query will also benefit from this content profile, even though it did not make the cut at the ITI planning committee.
7. Tech Cmte Evaluation
Effort Evaluation (as a % of Tech Cmte Bandwidth):
Responses to Issues:
Candidate Editor:
- TBA