Non-patient File Sharing (NPFS)
2.2.0-comment - ballot International flag

This page is part of the Non-patient File Sharing (NPFS) (v2.2.0-comment: Publication Ballot 1) based on FHIR R4. This is the current published version. For a full list of available versions, see the Directory of published versions

Non-patient File Sharing Home

Official URL: Version: 2.2.0-comment
Active as of 2023-08-04 Computable Name: IHE_ITI_NPFS

This profile defines how to enable the sharing of non-patient files.

Those files can be created, consumed and updated by many different systems involved in a wide variety of data sharing workflows (clinical workflow definition, domain policies sharing, stylesheets management, etc.). This profile identifies three actors: File Manager, File Consumer, and File Source. To fulfill use-case requirements, this profile defines four new transactions (Submit File [ITI-87], Search File [ITI-88], and Update DocumentReference [ITI-89]) and Retrieve File [ITI-109].

There are IHE profiles that define the content of files that are not patient-related; this profile does not require that the actors be able to process the contents of the files being shared. Understanding this profile does not require the knowledge of the files shared.

The NPFS Profile specifies transactions for the sharing of files. Any file type can be shared using this profile; however, specific guidance is given for three types of files:

Local policies may extend the types of files shared using NPFS and that can be classified using the metadata model described in this profile.

Organization of This Guide

This guide is organized into the following sections:

See also the Table of Contents and the index of Artifacts defined as part of this implementation guide.

Conformance Expectations

IHE uses the normative words: Shall, Should, and May according to standards conventions.

Must Support

The use of mustSupport in StructureDefinition profiles equivalent to the IHE use of R2 as defined in Appendix Z.

mustSupport of true - only has a meaning on items that are minimal cardinality of zero (0), and applies only to the source actor populating the data. The source actor shall populate the elements marked with MustSupport, if the concept is supported by the actor, a value exists, and security and consent rules permit. The consuming actors should handle these elements being populated or being absent/empty. Note that sometimes mustSupport will appear on elements with a minimal cardinality greater than zero (0), this is due to inheritance from a less constrained profile.