Generated Narrative: Requirements extended-operations-client-consent-server These requirements apply to the following actors: Consent Server System Consent Client System requirement-463 SHALL OperationDefinition FileConsent Links: Derived From: HL7 FAST Consent IG Satisfied By: http://build.fhir.org/ig/HL7/fhir-consent-management/OperationDefinition-file-consent.html requirement-133 SHALL The FileConsent operation is invoked as [base]/Consent/$fileConsent Links: Derived From: HL7 FAST Consent IG Satisfied By: http://build.fhir.org/ig/HL7/fhir-consent-management/OperationDefinition-file-consent.html requirement-134 SHALL The FileConsent operation input parameters SHALL conform to the FileConsentParameters profile For the most part, I'm not going to trace to everything in StructDefs, because the FHIR validator will check these. We may revisit this decision. Links: Derived From: HL7 FAST Consent IG Satisfied By: http://build.fhir.org/ig/HL7/fhir-consent-management/OperationDefinition-file-consent.json.html requirement-135 SHALL The FileConsent operation "consent" input parameter SHALL be 1..1 and a Consent resource Links: Derived From: HL7 FAST Consent IG Satisfied By: <a href="http://build.fhir.org/ig/HL7/fhir-consent-management/OperationDefinition-file-consent.json.html#:~:text=%22name%22%20%3A%20%22consent%22%2C%0A%20%20%20%20%20%20%22use%22%20%3A%20%22in%22%2C%0A%20%20%20%20%20%20%22min%22%20%3A%201%2C%0A%20%20%20%20%20%20%22max%22%20%3A%20%221%22%2C%0A%20%20%20%20%20%20%22documentation%22%20%3A%20%22The%20Consent%20instance%20to%20file%20(see%20Input%20Parameters%20Profile%20for%20conformance)%22%2C%0A%20%20%20%20%20%20%22type%22%20%3A%20%22Consent%22">http://build.fhir.org/ig/HL7/fhir-consent-management/OperationDefinition-file-consent.json.html requirement-166 SHALL The FileConsent operation "document" input parameter SHALL be 1..1 and any resource Links: Derived From: HL7 FAST Consent IG Satisfied By: <a href="http://build.fhir.org/ig/HL7/fhir-consent-management/OperationDefinition-file-consent.json.html#:~:text=%22name%22%20%3A%20%22document%22%2C%0A%20%20%20%20%20%20%22use%22%20%3A%20%22in%22%2C%0A%20%20%20%20%20%20%22min%22%20%3A%201%2C%0A%20%20%20%20%20%20%22max%22%20%3A%20%221%22%2C%0A%20%20%20%20%20%20%22documentation%22%20%3A%20%22Accompanying%20documentation%20for%20the%20Consent%20in%20the%20form%20of%20a%20DocumentReference%20or%20QuestionnaireResponse%20(see%20Input%20Parameters%20Profile%20for%20conformance)%22%2C%0A%20%20%20%20%20%20%22type%22%20%3A%20%22Resource%22">http://build.fhir.org/ig/HL7/fhir-consent-management/OperationDefinition-file-consent.json.html requirement-168 SHALL The FileConsent operation "return" output parameter SHALL be 0..1 and be an OperationOutcome Note no defined way to return Consent ID Links: Derived From: HL7 FAST Consent IG Satisfied By: <a href="http://build.fhir.org/ig/HL7/fhir-consent-management/OperationDefinition-file-consent.json.html#:~:text=%22name%22%20%3A%20%22return%22%2C%0A%20%20%20%20%20%20%22use%22%20%3A%20%22out%22%2C%0A%20%20%20%20%20%20%22min%22%20%3A%200%2C%0A%20%20%20%20%20%20%22max%22%20%3A%20%221%22%2C%0A%20%20%20%20%20%20%22documentation%22%20%3A%20%22Optional%20outcome%20of%20the%20operation%20call%22%2C%0A%20%20%20%20%20%20%22type%22%20%3A%20%22OperationOutcome%22">http://build.fhir.org/ig/HL7/fhir-consent-management/OperationDefinition-file-consent.json.html requirement-466 SHALL OperationDefinition RevokeConsent Links: Derived From: HL7 FAST Consent IG Satisfied By: http://build.fhir.org/ig/HL7/fhir-consent-management/OperationDefinition-revoke-consent.html requirement-438 SHALL The RevokeConsent operation is invoked as [base]/Consent/$revokeConsent Links: Derived From: HL7 FAST Consent IG Satisfied By: http://build.fhir.org/ig/HL7/fhir-consent-management/OperationDefinition-revoke-consent.html requirement-439 SHALL The RevokeConsent operation input parameters SHALL conform to the RevokeConsentParameters profile Links: Derived From: HL7 FAST Consent IG Satisfied By: http://build.fhir.org/ig/HL7/fhir-consent-management/OperationDefinition-revoke-consent.json.html requirement-440 SHALL The RevokeConsent operation "consent" input parameter SHALL be 1..1 and conform to the FASTConsent profile Links: Derived From: HL7 FAST Consent IG Satisfied By: http://build.fhir.org/ig/HL7/fhir-consent-management/OperationDefinition-revoke-consent.json.html requirement-447 SHALL The RevokeConsent operation "patient" input parameter SHALL be 1..1 and conform to the us-core-patient profile - See http://hl7.org/fhir/us/core/STU6.1/StructureDefinition-us-core-patient.html Consider tracking that Links: Derived From: HL7 FAST Consent IG Satisfied By: http://build.fhir.org/ig/HL7/fhir-consent-management/OperationDefinition-revoke-consent.json.html requirement-442 SHALL The RevokeConsent operation "document" input parameter SHALL be 0..1 and any resource Links: Derived From: HL7 FAST Consent IG Satisfied By: <a href="http://build.fhir.org/ig/HL7/fhir-consent-management/OperationDefinition-revoke-consent.json.html#:~:text=%22name%22%20%3A%20%22document%22%2C%0A%20%20%20%20%20%20%22use%22%20%3A%20%22in%22%2C%0A%20%20%20%20%20%20%22min%22%20%3A%200%2C%0A%20%20%20%20%20%20%22max%22%20%3A%20%221%22%2C%0A%20%20%20%20%20%20%22documentation%22%20%3A%20%22Accompanying%20documentation%20for%20the%20revocation%20of%20the%20Consent%20in%20the%20form%20of%20a%20DocumentReference%20or%20QuestionnaireResponse%20(see%20Input%20Parameters%20Profile%20for%20conformance)%22%2C%0A%20%20%20%20%20%20%22type%22%20%3A%20%22Resource%22">http://build.fhir.org/ig/HL7/fhir-consent-management/OperationDefinition-revoke-consent.json.html requirement-444 SHALL The RevokeConsent operation "return" output parameter SHALL be 0..1 and be an OperationOutcome Links: Derived From: HL7 FAST Consent IG Satisfied By: <a href="http://build.fhir.org/ig/HL7/fhir-consent-management/OperationDefinition-revoke-consent.json.html#:~:text=%22name%22%20%3A%20%22return%22%2C%0A%20%20%20%20%20%20%22use%22%20%3A%20%22out%22%2C%0A%20%20%20%20%20%20%22min%22%20%3A%200%2C%0A%20%20%20%20%20%20%22max%22%20%3A%20%221%22%2C%0A%20%20%20%20%20%20%22documentation%22%20%3A%20%22Optional%20outcome%20of%20the%20operation%20call%22%2C%0A%20%20%20%20%20%20%22type%22%20%3A%20%22OperationOutcome%22">http://build.fhir.org/ig/HL7/fhir-consent-management/OperationDefinition-revoke-consent.json.html requirement-467 SHALL OperationDefinition RecordDisclosure Links: Derived From: HL7 FAST Consent IG Satisfied By: http://build.fhir.org/ig/HL7/fhir-consent-management/OperationDefinition-record-disclosure.html requirement-445 SHALL The RecordDisclosure operation is invoked as [base]/AuditEvent/$recordDisclosure Links: Derived From: HL7 FAST Consent IG Satisfied By: http://build.fhir.org/ig/HL7/fhir-consent-management/OperationDefinition-record-disclosure.html requirement-446 SHALL The RecordDisclosure operation input parameters SHALL conform to the RecordDisclosureParameters profile Links: Derived From: HL7 FAST Consent IG Satisfied By: http://build.fhir.org/ig/HL7/fhir-consent-management/OperationDefinition-record-disclosure.json.html requirement-451 SHALL The RecordDisclosure operation "disclosure" input parameter SHALL be 1..1 and an AuditEvent resource Links: Derived From: HL7 FAST Consent IG Satisfied By: <a href="http://build.fhir.org/ig/HL7/fhir-consent-management/OperationDefinition-record-disclosure.json.html#:~:text=%22name%22%20%3A%20%22disclosure%22%2C%0A%20%20%20%20%20%20%22use%22%20%3A%20%22in%22%2C%0A%20%20%20%20%20%20%22min%22%20%3A%201%2C%0A%20%20%20%20%20%20%22max%22%20%3A%20%221%22%2C%0A%20%20%20%20%20%20%22documentation%22%20%3A%20%22An%20AuditEvent%20detailing%20the%20disclosure%20(see%20Input%20Parameters%20Profile%20for%20conformance)%22%2C%0A%20%20%20%20%20%20%22type%22%20%3A%20%22AuditEvent%22">http://build.fhir.org/ig/HL7/fhir-consent-management/OperationDefinition-record-disclosure.json.html requirement-449 SHALL The RecordDisclosure operation "consent" input parameter SHALL be 1..1 and conform to the FASTConsent profile Links: Derived From: HL7 FAST Consent IG Satisfied By: http://build.fhir.org/ig/HL7/fhir-consent-management/OperationDefinition-record-disclosure.json.html requirement-453 SHALL The RecordDisclosure operation "return" output parameter SHALL be 0..1 and be an OperationOutcome Links: Derived From: HL7 FAST Consent IG Satisfied By: <a href="http://build.fhir.org/ig/HL7/fhir-consent-management/OperationDefinition-record-disclosure.json.html#:~:text=%22name%22%20%3A%20%22return%22%2C%0A%20%20%20%20%20%20%22use%22%20%3A%20%22out%22%2C%0A%20%20%20%20%20%20%22min%22%20%3A%200%2C%0A%20%20%20%20%20%20%22max%22%20%3A%20%221%22%2C%0A%20%20%20%20%20%20%22documentation%22%20%3A%20%22Optional%20outcome%20of%20the%20operation%20call%22%2C%0A%20%20%20%20%20%20%22type%22%20%3A%20%22OperationOutcome%22">http://build.fhir.org/ig/HL7/fhir-consent-management/OperationDefinition-record-disclosure.json.html
Extended Operations Client Admin Service
HL7 International / Community Based Collaborative Care
Extended Operations Requirements for Client Admin Service
The FileConsent operation is invoked as [base]/Consent/$fileConsent
The FileConsent operation input parameters SHALL conform to the FileConsentParameters profile For the most part, I'm not going to trace to everything in StructDefs, because the FHIR validator will check these. We may revisit this decision.
The FileConsent operation "consent" input parameter SHALL be 1..1 and a Consent resource
The FileConsent operation "document" input parameter SHALL be 1..1 and any resource
The FileConsent operation "return" output parameter SHALL be 0..1 and be an OperationOutcome Note no defined way to return Consent ID
The RevokeConsent operation is invoked as [base]/Consent/$revokeConsent
The RevokeConsent operation input parameters SHALL conform to the RevokeConsentParameters profile
The RevokeConsent operation "consent" input parameter SHALL be 1..1 and conform to the FASTConsent profile
The RevokeConsent operation "patient" input parameter SHALL be 1..1 and conform to the us-core-patient profile - See http://hl7.org/fhir/us/core/STU6.1/StructureDefinition-us-core-patient.html - Consider tracking that
The RevokeConsent operation "document" input parameter SHALL be 0..1 and any resource
The RevokeConsent operation "return" output parameter SHALL be 0..1 and be an OperationOutcome
The RecordDisclosure operation is invoked as [base]/AuditEvent/$recordDisclosure
The RecordDisclosure operation input parameters SHALL conform to the RecordDisclosureParameters profile
The RecordDisclosure operation "disclosure" input parameter SHALL be 1..1 and an AuditEvent resource
The RecordDisclosure operation "consent" input parameter SHALL be 1..1 and conform to the FASTConsent profile
The RecordDisclosure operation "return" output parameter SHALL be 0..1 and be an OperationOutcome