Unattributed Code Systems

• http://unstats.un.org/unsd/methods/m49/m49.htm
• https://profiles.ihe.net/ITI/BALP/CodeSystem/BasicAuditEntityType
• https://profiles.ihe.net/ITI/NPFS/CodeSystem/NPFSclasscode
• urn:ihe:event-type-code
• urn:oid:1.3.6.1.4.1.19376.1.5.3.1.5
• urn:oid:2.16.840.1.113883.2.9.3.3.6.1.6

Copyright Fragment

This fragment is available on download.html

Copyright and Registered Trademark Uses

• IG © 2021+ IHE IT Infrastructure Technical Committee. Package ihe.iti.npfs#2.2.1-current based on FHIR 4.0.1. Generated 2025-04-28 Links: Table of Contents | QA Report | New Issue | Issues Version History | CC0 | Propose a changeexternal ( src )
• hl7.fhir.us.hai: Healthcare Associated Infection Implementation Guide ®© HL7 | CC0 ( src )
• Non-patient File Sharing (NPFS), published by IHE IT Infrastructure Technical Committee. This guide is not an authorized publication; it is the continuous build for version 2.2.1-current built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/IHE/ITI.NPFS/ and changes regularly. See the Directory of published versions ( src )
• These codes are excerpted from Digital Imaging and Communications in Medicine (DICOM) Standard, Part 16: Content Mapping Resource, Copyright © 2011 by the National Electrical Manufacturers Association. Show Usage * DICOM Controlled Terminology Definitions: AuditRetrieveFileConsumer, AuditRetrieveFileManager... Show 6 more , AuditSearchFileConsumer, AuditSearchFileManager, AuditSubmitFileManager, AuditSubmitFileSource, AuditUpdateDocumentReferenceManager and AuditUpdateDocumentReferenceSource * Audit Event ID: AuditRetrieveFileConsumer, AuditRetrieveFileManager... Show 4 more , AuditSearchFileConsumer, AuditSearchFileManager, AuditUpdateDocumentReferenceManager and AuditUpdateDocumentReferenceSource ( src )
• This material contains content from LOINC. LOINC is copyright © 1995-2020, Regenstrief Institute, Inc. and the Logical Observation Identifiers Names and Codes (LOINC) Committee and is available at no cost under the license. LOINC® is a registered United States trademark of Regenstrief Institute, Inc. Show Usage * LOINC: DocumentReferenceCategory and NPFSDocumentReference ( src )
• This material derives from the HL7 Terminology (THO). THO is copyright ©1989+ Health Level Seven International and is made available under the CC0 designation. For more licensing information see: https://terminology.hl7.org/license.html Show Usage * Audit event entity type: AuditRetrieveFileConsumer, AuditRetrieveFileManager... Show 6 more , AuditSearchFileConsumer, AuditSearchFileManager, AuditSubmitFileManager, AuditSubmitFileSource, AuditUpdateDocumentReferenceManager and AuditUpdateDocumentReferenceSource * AuditEventEntityRole: AuditRetrieveFileConsumer, AuditRetrieveFileManager... Show 6 more , AuditSearchFileConsumer, AuditSearchFileManager, AuditSubmitFileManager, AuditSubmitFileSource, AuditUpdateDocumentReferenceManager and AuditUpdateDocumentReferenceSource * ActCode: Bundle/ex-CreateDocumentBundle, Bundle/ex-ReplaceDocumentBundle, Bundle/ex-UpdateDocumentBundle and DocumentReference/12345 * ActReason: Bundle/ex-CreateDocumentBundle, Bundle/ex-ReplaceDocumentBundle... Show 5 more , Bundle/ex-UpdateDocumentBundle, DocumentReference/12345, DocumentReference/ex-DocumentReferenceMinimal, Patient/ex-patient and Practitioner/ex-practitioner * Confidentiality: Bundle/ex-CreateDocumentBundle, Bundle/ex-ReplaceDocumentBundle, Bundle/ex-UpdateDocumentBundle and DocumentReference/12345 * ParticipationType: AuditRetrieveFileConsumer, AuditRetrieveFileManager, AuditSearchFileConsumer and AuditSearchFileManager ( src )
• ® ( src )

External References

Type	Reference	Content
web	profiles.ihe.net	Recommend ATNA , encouraged IHE-IUA or SMART-app-launch
web	profiles.ihe.net	Recommend ATNA , encouraged IHE-IUA or SMART-app-launch
web	example.com	http://example.com/nowhere.txt
web	profiles.ihe.net
web	profiles.ihe.net
web	github.com	Non-patient File Sharing (NPFS), published by IHE IT Infrastructure Technical Committee. This guide is not an authorized publication; it is the continuous build for version 2.2.1-current built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/IHE/ITI.NPFS/ and changes regularly. See the Directory of published versions
web	www.ihe.net	IG © 2021+ IHE IT Infrastructure Technical Committee . Package ihe.iti.npfs#2.2.1-current based on FHIR 4.0.1 . Generated 2025-04-28 Links: Table of Contents | QA Report | New Issue | Issues Version History | | Propose a change
web	github.com	Links: Table of Contents | QA Report | New Issue | Issues Version History | | Propose a change
web	github.com	Links: Table of Contents | QA Report | New Issue | Issues Version History | | Propose a change
web	profiles.ihe.net	Links: Table of Contents | QA Report | New Issue | Issues Version History | | Propose a change
web	www.ihe.net	Links: Table of Contents | QA Report | New Issue | Issues Version History | | Propose a change
web	profiles.ihe.net	The File Manager may return other HTTP Status Codes. Guidance on handling Access Denied related to use of 200, 403 and 404 can be found in ITI TF-2: Appendix Z.7 .
web	profiles.ihe.net	File Managers implementing this transaction shall provide a CapabilityStatement Resource as described in ITI TF-2: Appendix Z.3 indicating the transaction has been implemented.
web	profiles.ihe.net	The files are not Patient specific, but they may have other needs for security controls, such as business knowledge restrictions. Thus, the use of Security may be applicable. Actors involved in this transaction should be aware that even if the Resources exchanged do not contain PHI or other private information, retrieving those Resources could compromise patient care or have other legal ramifications. For general security considerations, see ITI TF-2: Appendix Z.8 (currently in the Appendix Z on HL7 FHIR Trial Implementation Supplement).
web	profiles.ihe.net	The File Consumer when grouped with ATNA Secure Node or Secure Application Actor shall be able to record a Retrieve File Consumer Audit Event Log .
web	profiles.ihe.net	The File Manager when grouped with ATNA Secure Node or Secure Application Actor shall be able to record a Retrieve File Manager Audit Event Log .
web	profiles.ihe.net	The File Source shall submit FHIR resources in either XML format or JSON format. Values for media-type of the request message are defined in the ITI TF-2: Appendix Z.6 (currently in the Appendix Z on HL7 FHIR Trial Implementation Supplement).
web	profiles.ihe.net	See ITI TF-2: Appendix W for informative implementation material for this transaction.
web	www.ihe.net	If the file submitted is a Workflow Definition template, the type element could be valued with the workflow definition reference of the Workflow Definition profile (see workflowDefinitionReference as defined by the XDW Profile; see ITI TF-3: 5.4.2.2 ).
web	www.ihe.net	If the file submitted is a Workflow Definition template, the masterIdentifier element shall be valued with the workflowDefinitionReference as defined by the XDW Profile ( see ITI TF-3: 5.4.2.2 ) .
web	profiles.ihe.net	If the file submitted is a Patient Privacy Policy ( see ITI TF-1: 19.2.1 Basic Patient Privacy Consent ), the masterIdentifier element shall be valued with the associated Patient Privacy Policy Identifier.
web	profiles.ihe.net	The File Manager shall support all the media-types defined in ITI TF-2: Appendix Z.6 (currently in the Appendix Z on HL7 FHIR Trial Implementation Supplement).
web	profiles.ihe.net	The File Manager shall support all the media-type defined in ITI TF-2: Appendix Z.6 (currently in the Appendix Z on HL7 FHIR Trial Implementation Supplement).
web	profiles.ihe.net	The files are not Patient specific, but they may have other needs for security controls, such as business knowledge restrictions. Thus the use of Security may be applicable. Actors involved in this transaction should be aware that even if the Resources exchanged do not contain PHI or other private information, actions such creating, updating, or replacing those Resources could compromise patient care or have other legal ramifications. For general security considerations, see ITI TF-2: Appendix Z.8 (currently in the Appendix Z on HL7 FHIR Trial Implementation Supplement).
web	profiles.ihe.net	The File Source, when grouped with ATNA Secure Node or Secure Application Actor, shall be able to record a Submit File Source Audit Event Log .
web	profiles.ihe.net	The File Manager, when grouped with ATNA Secure Node or Secure Application Actor, shall be able to record a Submit File Manager Audit Event Log .
web	profiles.ihe.net	This parameter, of type token, specifies the identifier of the author that has submitted the file. See ITI TF-2: Appendix Z.2.2 (currently in the Appendix Z on HL7 FHIR Trial Implementation Supplement) for use of the token data type.
web	profiles.ihe.net	See ITI TF-2: Appendix Z.6 (currently in the Appendix Z on HL7 FHIR Trial Implementation Supplement) for details.
web	profiles.ihe.net	Guidance on handling Access Denied related to use of 200, 403 and 404 can be found in ITI TF- 2: Appendix Z.7 (currently in the Appendix Z on HL7 FHIR Trial Implementation Supplement).
web	profiles.ihe.net	The response shall adhere to the FHIR Bundle constraints specified in ITI TF-2: Appendix Z.1 (currently in the Appendix Z on HL7 FHIR Trial Implementation Supplement).
web	profiles.ihe.net	The files are not Patient specific, but they may have other needs for security controls, such as business knowledge restrictions. Thus the use of Security may be applicable. Actors involved in this transaction should be aware that even if the Resources exchanged do not contain PHI or other private information, exchange of those Resources could compromise patient care or have other legal ramifications. For general security considerations, see ITI TF-2: Appendix Z.8 .
web	profiles.ihe.net	The File Consumer when grouped with ATNA Secure Node or Secure Application Actor shall be able to record a Search File Consumer Audit Event Log .
web	profiles.ihe.net	The File Manager when grouped with ATNA Secure Node or Secure Application Actor shall be able to record a Search File Manager Audit Event Log .
web	profiles.ihe.net	The File Source shall submit the DocumentReference Resource in either XML format or JSON format. Values accepted for media-type of the request message are defined in the ITI TF-2: Appendix Z.6 (currently in the Appendix Z on HL7 FHIR Trial Implementation Supplement).
web	profiles.ihe.net	The File Manager shall support all the media-type listed in ITI TF-2: Appendix Z.6 (currently in the Appendix Z on HL7 FHIR Trial Implementation Supplement).
web	profiles.ihe.net	The files are not Patient specific, but they may have other needs for security controls, such as business knowledge restrictions. Thus, the use of Security may be applicable. Actors involved in this transaction should be aware that even if the Resources exchanged do not contain PHI or other private information, updating those Resources could compromise patient care or have other legal ramifications. For general security considerations, see ITI TF-2: Appendix Z.8 .
web	profiles.ihe.net	The File Source when grouped with ATNA Secure Node or Secure Application Actor shall be able to record a Update DocumentReference Source Audit Event Log .
web	profiles.ihe.net	The File Manager when grouped with ATNA Secure Node or Secure Application Actor shall be able to record a Update DocumentReference Manager Audit Event Log .
web	en.wikipedia.org	Both Bundle.link and Bundle.entry.link are defined to support providing additional context when Bundles are used (e.g. HATEOAS ).
web	github.com	The source code for this Implementation Guide can be found on https://github.com/IHE/ITI.NPFS .
web	profiles.ihe.net	Workflow Definitions: files which define the processing rules for a specific clinical/administrative workflow (see ITI TF-1: 30.4.1.1 “XDW Workflow Architecture” for additional information).
web	profiles.ihe.net	Privacy Domain Policies: files which describe a specific privacy policy that applies to, or may be agreed by the patient (see ITI TF-1: 19.2 “Creating Patient Privacy Policies” for further details).
web	profiles.ihe.net	IHE uses the normative words: Shall, Should, and May according to standards conventions .
web	profiles.ihe.net	The use of mustSupport in StructureDefinition profiles equivalent to the IHE use of R2 as defined in Appendix Z .
web	github.com	IHE welcomes New Issues from the GitHub community. For those without GitHub access, issues may be submitted to the Public Comment form .
web	www.ihe.net	IHE welcomes New Issues from the GitHub community. For those without GitHub access, issues may be submitted to the Public Comment form .
web	github.com	As issues are submitted they will be managed on the NPFS GitHub Issues , where discussion and workarounds may be found. These issues, when critical, will be processed using the normal IHE Change Proposal management and balloting. It is important to note that as soon as a Change Proposal is approved, it carries the same weight as a published Implementation Guide (i.e., it is testable at an IHE Connectathon from the time it is approved, even if it will not be integrated until several months later).
web	wiki.ihe.net	As issues are submitted they will be managed on the NPFS GitHub Issues , where discussion and workarounds may be found. These issues, when critical, will be processed using the normal IHE Change Proposal management and balloting. It is important to note that as soon as a Change Proposal is approved, it carries the same weight as a published Implementation Guide (i.e., it is testable at an IHE Connectathon from the time it is approved, even if it will not be integrated until several months later).
web	www.ihe.net	As issues are submitted they will be managed on the NPFS GitHub Issues , where discussion and workarounds may be found. These issues, when critical, will be processed using the normal IHE Change Proposal management and balloting. It is important to note that as soon as a Change Proposal is approved, it carries the same weight as a published Implementation Guide (i.e., it is testable at an IHE Connectathon from the time it is approved, even if it will not be integrated until several months later).
web	github.com	NPFS_010 : This document begins the definition of a value set for the class element. How do we complete the value set for this profile? Suggestions are requested. How do we coordinate this value set with other Document Sharing profiles? Suggestions are requested.
web	github.com	NPFS_012 : This document does not require the use of profile tags to identify compliant resources. Use of profile tags will also allow the File Consumer to search just for resources that matches this profile in a FHIR Server that store different types of resources. Readers are required to provide feedback on this topic.
web	github.com	NPFS_013 : DocumentReference.subject is set to 0..0; the .subject element may still be useful for subjects that are not patient. Practitioner – this is individual, so I wonder if we really want NPFS to also be (non practitioner)? Group – groups can be made up of Patients. So it is not clear how we would allow Group, but not allow Groups of Patients. Device – often a Device is associated with a Patient, although many Devices are just Devices. Allowing Device might be the most clear use-case. Seems we should have a positive use-case to drive deviation from 0..0. Suggestions are requested. Note that in the future, using FHIR R5, subject can be a reference to ANY kind of Resource. This is just mentioned as foreshadowing, it should not be part of the current profile.
web	profiles.ihe.net	Editor, add the following new or modified actors to the IHE Technical Frameworks General Introduction Appendix A :
web	profiles.ihe.net	Editor, add the following new or modified transactions to the IHE Technical Frameworks General Introduction Appendix B :
web	profiles.ihe.net	Editor, add the following new or modified terms to the IHE Technical Frameworks General Introduction Appendix D :
web	gazelle.ihe.net	The tests listed below are defined in Gazelle Master Model and are performed by systems testing NPFS at IHE Connectathons.
web	profiles.ihe.net	Workflow Definitions: files which define the processing rules for a specific clinical/administrative workflow (see ITI TF-1: 30.4.1.1 “XDW Workflow Architecture” )
web	profiles.ihe.net	Privacy Domain Policies: files which describe a specific privacy policy that applies to, or may be agreed to, by a patient (see ITI TF-1: 19.2 “Creating Patient Privacy Policies” )
web	www.ihe.net	This section defines the actors, transactions, and/or content modules in this profile. General definitions of actors are given in the Technical Frameworks General Introduction Appendix A at https://www.ihe.net/resources/technical_frameworks/#GenIntro .
web	profiles.ihe.net	Then, when the patient selects a Privacy Policy, the nurse uses a Basic Patient Privacy Consent (BPPC) Content Creator Actor (see ITI TF-1: 19 ) to create the patient’s Privacy Policy Consent document for the patient.
web	profiles.ihe.net	Although this profile does not require actors to audit the transactions that exchange non-patient files, grouping with an ATNA Secure Node or Secure Application is strongly encouraged in order to track file and metadata creation and update. For further considerations about Audit record refer to BALP profile .

Internal Images