1 / 10

ebXML and XDS

XDS Patient Identifier Source. Patient Id Feed. ebXML and XDS. XDS Validation: Patient Id is known Vocabulary Checking Set to approve if registration OK otherwise, roll-back registration. XDS Registry. ebXML Registry. XDS Validation. ebXML Compliance:

brynne-zamora
Download Presentation

ebXML and XDS

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. XDS Patient IdentifierSource Patient Id Feed ebXML and XDS • XDS Validation: • Patient Id is known • Vocabulary Checking • Set to approve if registration OK otherwise, roll-back registration XDS Registry ebXML Registry XDS Validation • ebXML Compliance: • All transaction are valid ebXML transactions • Sequencing may be simplified • ebXML query against a valid Registry model specialisation Validate Document RegisterDocument Set XDS Repository Provide & RegisterDocument Set

  2. Querying for Documents Patient Id • The five primary search keys for finding a document: • Which Patient ? • What Type of Practice Setting ? • Between 10 and 100 • What Type of Facility ? • Between 10 and 50 • What Type of Document ? • Between 100 and 1000 • What timeframe ? Practice Setting Facility Type Document Type Time of Services 3 Independent dimensions. One with 3 interrelated sub-dimensions

  3. Document Availability Management Registration in progress Available for Patient Care Availability Status Visible to a Document Consumer Availability Status Visible to a Document Source Deprecated (or Obsolete) Deleted Availability Status Change under the Control of Original Document Source and Patient (if allowed in Affinity Domain)

  4. Addendum and Original Registry Entries shall be similar. Consumer may always find all original and addendum by Doc SetId. Document Parent Id Document LifeCycle Management Addendum Doc Set Id Document 1 (Available) Replacement doc and availability status change shall be part of the same submission set. Parent Id Document 1 (Deprecated) Replacement Document Doc Set Id Parent Id A transformed document may be part of the same submission set or not. Only way to find if a document has transforms is to query using SetId. Document 1 Document 2 (transform) Doc Set Id Document Set Id shall be under the control of the Source of Original Version number is an optional/unused field (policy to increment ?)

  5. Patient Identification Management

  6. SubmissionSet SubmissionSet SubmissionSet New Doc New Doc Prev Doc New Doc Prev Doc New Doc New Doc Collaborative Folder B Collaborative Folder A Submission Set & Folders

  7. Submission Set or Submission Folder ? SubmissionFolder SubmissionFolder SubmissionFolder Add a single clinical meaning code ! Suggests making Collaborative Folders a Source and Registry Option New Doc New Doc Prev Doc New Doc Prev Doc New Doc Query: Viewsonly Folders New Doc Collaborative Folder B Collaborative Folder A

  8. Submission Set & Folders

  9. Submission Set & Folders

  10. SubmissionSet (Reqested) New Doc New Doc New Doc A Registry/Repository detects re-submission SubmissionSet (Registered) New Doc New Doc Prev Doc Re-Submission SubmissionSet • Alternatives ? • Multiple Registry Entry/Doc with same UID confuses Consumer • One Registry Entry with multiple Docs complex, not useful for Consumer, and likelihood of exact same Registry Entry with same Doc UID+Hash in re-submission is small. Goal is to detect and solve re-submission when happen Suggest making this detection and correction an option New Doc A New Doc

More Related