Template talk:Network Architecture - Revision history

IVSWikiBlue at 19:21, 23 January 2026

2026-01-23T19:21:35Z

IVSWikiBlue at 19:19, 23 January 2026

2026-01-23T19:19:04Z

IVSWikiBlue at 19:18, 23 January 2026

2026-01-23T19:18:57Z

IVSWikiBlue at 14:23, 22 January 2026

2026-01-22T14:23:22Z

IVSWikiBlue: Created page with "{{Section | title =

Network Architecture

| content = Below is a diagram of a sensitive network environment, where in-transit encryption is a requirement. This type..."

2026-01-22T14:22:46Z

Created page with "{{Section | title = <h1>Network Architecture</h1> | content = Below is a diagram of a sensitive network environment, where in-transit encryption is a requirement. This type..."

New page

{{Section | title = <h1>Network Architecture</h1> | content =

Below is a diagram of a sensitive network environment, where in-transit encryption is a requirement. This type of network architecture is typical of environments that are using the system to capture / observe actual patient interactions within clinical training environments.

{{img - resize| file = Network_testing_img.webp}}

{{Aside | content = For SSL, we will need the customer to set up a DNS name for the server <em>(example ivs-valt.mysite.edu)</em>. We will also need a wildcard or generated signed certificate that is compatible with nginx and can be applied by an IVS engineer. LetsEncrypt may also be utilized.}}
}}

← Older revision		Revision as of 19:18, 23 January 2026
Line 2:		Line 2:

	Below is a diagram of a sensitive network environment, where in-transit encryption is a requirement. This type of network architecture is typical of environments that are using the system to capture / observe actual patient interactions within clinical training environments.		Below is a diagram of a sensitive network environment, where in-transit encryption is a requirement. This type of network architecture is typical of environments that are using the system to capture / observe actual patient interactions within clinical training environments.
−

	{{img - resize\| file = Network_testing_img.webp}}		{{img - resize\| file = Network_testing_img.webp}}

← Older revision		Revision as of 14:23, 22 January 2026
Line 1:		Line 1:
−	{{~~Section~~ \| title = ~~<h1>~~Network Architecture~~</h1>~~ \| content =	+	{{Article - Manual \| title = Network Architecture\| content =

	Below is a diagram of a sensitive network environment, where in-transit encryption is a requirement. This type of network architecture is typical of environments that are using the system to capture / observe actual patient interactions within clinical training environments.		Below is a diagram of a sensitive network environment, where in-transit encryption is a requirement. This type of network architecture is typical of environments that are using the system to capture / observe actual patient interactions within clinical training environments.

@@ Line 1: / Line 1: @@
 {{Article - Manual | title = Network Architecture| content =
-Below is a diagram of a sensitive network environment, where in-transit encryption is a requirement.  This type of network architecture is typical of environments that are using the system to capture / observe actual patient interactions within clinical training environments.
+Below is a diagram of a sensitive network environment, where in-transit encryption is a requirement. This type of network architecture is typical of environments that are using the system to capture / observe actual patient interactions within clinical training environments.
 {{img - resize| file = Network_testing_img.webp}}
-{{Aside | content = For SSL, we will need the customer to set up a DNS name for the server <em>(example ivs-valt.mysite.edu)</em>.  We will also need a wildcard or generated signed certificate that is compatible with nginx and can be applied by an IVS engineer. LetsEncrypt may also be utilized.}}
+{{Aside - Helpful | content = Want to see more information about our [[Network Requirements]]?}}
 }}