Generator of IPS documents (such as personal health records, health information exchanges or electronic health records)
Receiver of IPS documents
No advance preparation is specifically required, although reviewing the implementation guide and examples of IPS samples will be helpful (https://github.com/jddamore/IPSviewer/tree/main/samples)
Roles & Scenarios
IPS Document Creator
Creates or updates a FHIR IPS document (Bundle containing a Composition and supporting resources) from source data. The source data likely will be existing data on
a FHIR server, but this can be done using whatever means are appropriate, including manual creation, assembling documents from other resources, transforming from
a CDA IPS document, etc. Submits that document to a FHIR server.
IPS Document Consumer
Retrieves a FHIR IPS document and/or individual component resource instances created by the Document Creator from the FHIR server and does
one or more of the following: a) validates the document and/or component resource instances against the IPS Clinical Document profile, b) displays the document
and/or discrete data components in a browser (or by other means), c) translates the coded and/or narrative data to a different language for display, or d) translates the
coded data to different code system(s) used in a jurisdiction that is different from the source.
IPS Document Processor
Uses a FHIR IPS document and/or individual component resource instances for the purpose of creating/updating other kinds of IPS based documents as for example
Precondition: Success Criteria:
- Usage of tools to validate IPS conformance
- Usage of tools to visualize IPS content
- Conformant IPS documents that validate without errors
- Successful visualization of IPS documents
- Advancement and feedback on the implementation guidance
No test scripts at this time.
Security and Privacy Considerations:
No plans to test security at this time. Privacy and confidentiality are within scope for discussion.