Brainscape's Knowledge GenomeTM

Browse over 1 million classes created by top students, professors, publishers, and experts.


See full index

HealthShare > Designing Productions > Flashcards

Designing Productions Flashcards

1
Q

How would you navigate to the namespace page?

A 
system administration
configuration
system configuration
namespaces
go
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

From namespaces, how would you create a new namespace?

A 
Create New Namespace
name the namespace
create new database (if desired) next to select an existing database for globals field
name the database
add database directory
next
next
next
finish
follow same steps for routines
save
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

When should you use system packages for custom code?

A

never

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

When should you have separate databases for code and data?

A

always

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

How many productions should exist in a namespace?

A

one

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

How many messages routers would you typically have for each business service?

A

one

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

How many routing rules should you have for each downstream destination requiring that message?

A

one

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

It is a best practice to have how many business operations for each external application being sent HL7 messages?

A

one

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Where in the production would you be able to filter the display to show only configuration components of grouping that you defined?

A

the category dropdown

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

When should naming conventions be determined?

A

before development

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

What keyword is suggested for business services?

A

from

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

what keyword is suggested for business operations?

A

to

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

what keyword is suggested for use with routers?

A

router

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

What is an example naming convention for DTLs?

A

SourceAppNameMessageTypeToTargetAppNameMessageType

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

what keyword is suggested for use with routing rules?

A

rules

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

How would you enable testing in a production?

A

production settings
development and debugging
check testing enabled

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

How would you limit incoming connections to one or more ip addresses?

A

select the tcp business service
connection settings
enter a comma separated list of ip addresses in the allowed ip addresses field

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

In a filename field, what does %f mean?

A

use the incoming file name

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

In the filename field, what does %Q mean?

A

add a timestamp

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

What ACK modes are available on a TCP business service?

A

Never: Do not send back any ACK.
Immediate: Send back (commit) ACK reply message immediately upon receipt of the inbound message.
Application: If message passes validation, wait for ACK from target config item and forward it back when it arrives.
MSH-determined: Send back ACK reply messages as requested in the MSH header of the incoming message.
Byte: Send back an immediate single ACK-code byte instead of an ACK message. Byte ASCII code 6 = ‘OK’, ASCII code 21 = ‘Error’

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
21
Q

What NACK modes are available on a TCP business service?

A 
ContentE = Use MSA error code 'E' to report errors in message content and code 'R' to reject due to (retryable) system errors.
ContentR = Return 'R' for content errors, 'E' for system errors.
AllE = Return 'E' for all content and system errors.
AllR = Return 'R' for all content and system errors.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
22
Q

What field in a business service specifies where the inbound message will be sent?

A

Target Config Names

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
23
Q

What field in a business service specifies the HL7 version that is acceptable for an incoming message?

A

Message Schema Category

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
24
Q

How would you enable validation in a business process

A

enter 1 or flags (e.g. dmz) in the Validation field

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
25
Q

What ACK types are availiable to a business process?

A

Commit — ACK is returned when the message is received

Application — ACK is returned once all processing has been successfully completed

26
Q

What is a NACK?

A

A negative ACK (NACK) message acknowledges that the destination is aware of the transmission but did not capture the message.

27
Q

Where would you enter default settings?

A

Ensemble
Configure
System Default Settings

or the arrow/page icon

28
Q

pool size

A

Number of jobs to start for this config item.
Default value:
0 for Business Processes (i.e. use shared Actor Pool)
1 for FIFO message router Business Processes (i.e. use a dedicated job)
1 for Business Operations
0 for adapterless Business Services
1 for others
For TCP based Services with JobPerConnection=1, this value is used to limit the number of connection jobs if its value is greater than 1. A value of 0 or 1 places no limit on the number of connection jobs.

29
Q

actor pool size

A

Unlike other types of business host, a business process has the option of sharing jobs from a public pool; this pool is called the actor pool or Ens.Actor. You can configure the Actor Pool Size for the production. Actors in the production-wide actor pool have no affiliation with or knowledge of a specific business process. Any business process that has a private Pool Size of 0 can use jobs from the public actor pool.
The choice as to whether or not a business process should use its own private pool or the public pool depends on the needs of the production. Any nonzero value for a private Pool Size ensures that the business process only uses jobs from its private pool. If you want any business process to use jobs from the actor pool, its private Pool Size must be 0. The default Ensemble configuration allows 1 job in the private pool for each business host, and 2 jobs in the production-wide actor pool. This means that if you want business processes to share the actor pool it does not happen automatically; you must set their individual Pool Size settings to 0.

In situations other than healthcare, private pools of a size 1 or greater can be useful for fast-running business processes in a production that also includes slow-running business processes. A fast-running business process can have a private pool to ensure that its requests never get stuck in the public actor queue behind accumulated requests for the slow-running business processes.
If every business process in your production has a private pool, then the Actor Pool Size for the production can be 0. On the other hand, if your production includes many business processes that use the public actor pool, you can raise the Actor Pool Size for the production from the default of 2 to prevent bottlenecks when many business processes are running. InterSystems recommends that, as a maximum, you set the Actor Pool Size equal to the number of CPUs in your Ensemble server machine. You could set the number higher, but at any one time there are only as many jobs available as there are CPUs.

30
Q

Archive IO

A

Settings&raquo_space; Development and Debugging

Common to business services and operations.

If set, the adapter logs in the Ensemble I/O archive each input and output communication it shares with the external system.

In the message trace this is represented by two blue arrows (pointing right and left) and will be displayed in IO columns to the left of services or to the right of operations.

31
Q

call interval

A

settings > basic settings

The minimum interval between invocations of the adapter by the Ensemble framework. For adapters that poll for external events, this is the polling interval. However, most polling adapters will process all inputs immediately if several are detected at one time. This is also the interval at which each Business Service will check for shutdown requests.

Specifies the number of seconds that the adapter will listen for incoming data from its configured source, before checking for a shutdown signal from the production framework.
If the adapter finds input, it acquires the data and passes it to the business service. The business service processes the data, and then the adapter immediately begins waiting for new input. This cycle continues whenever the production is running and the business service is enabled and scheduled to be active.
The default is 5 seconds. The minimum is 0.1 seconds.

32
Q

Alert Grace Period

A

settings&raquo_space; alerting control

Specifies an optional grace period during which errors relating to external connections do not trigger alerts (even if Alert On Error is True). If the error condition still exists after the grace period, the business service triggers an alert; otherwise no alert is triggered.

33
Q

Inactivity timeout

A

settings&raquo_space; alerting control

Common to all business hosts. A business host has an Inactive status after it has not received any messages within the number of seconds specified by the Inactivity Timeout field. The Ensemble Monitor Service periodically reviews the status of business services and business operations within the production, and marks the item as Inactive if it has not done anything within the Inactivity Timeout period.
The default value is 0 (zero). If this setting is 0, the business host will never be marked Inactive, no matter how long it stands idle.

34
Q

Schedule

A

settings&raquo_space; Additional Settings

Common to all business hosts. An optional command string that schedules stop and start times for the business host. The string is a comma-separated list of event specifications, each of which has the following format:
action:YYYY-MM-DDThh:mm:ss
Where action is either START or STOP to indicate the desired event.

For example, to start the configuration item every day at 8 a.m. and stop it every day at 5 p.m. you could use the following schedule string:

START:--T08:00:00,STOP:--T17:00:00

35
Q

Throttle Delay

A

settings&raquo_space; Additional Settings

Common to business services and business operations. Specifies a period of forced idleness before processing the next message, in milliseconds. The default is 0.

It applies on a per-job basis so that operations with Pool Size greater than 1 and services with JobPerConnection as true can still generate multiple messages within the interval.

36
Q

SendSuperSession

A

business operation&raquo_space; settings&raquo_space; additional settings

The SendSuperSession is a Boolean setting that controls whether the outbound adapter creates a SuperSession header in the HTTP header and generates an identifier for it.

37
Q

What is a supersession?

A

supersessions involve messages that cross from one namespace to another

38
Q

Foreground

A

settings&raquo_space; development and debugging

Common to business services and operations. By default, this check box is clear. Select it for debugging or diagnostic purposes only. Jobs in operational systems almost never run in the foreground. When you select the Foreground check box, any system jobs used by the business service run in a Terminal window at the front of the console display. This allows Ensemble to display debugging or trace messages in that window.

39
Q

Log Trace Events

A

settings&raquo_space; development and debugging

Common to all business hosts. Trace messages are informational text messages that Ensemble can deliver to the Terminal window (if you select the Foreground check box) and, optionally, to the Ensemble Event Log. Trace messages are unrelated to Visual Trace, which provides a graphical view of Ensemble message objects as they travel through a production.
By default, the Log Trace Events check box is clear. When selected, it enables logging of all trace messages issued by this business host. Logging means that Ensemble writes the trace messages to the console Terminal window (if your job is running in the foreground) and it also stores copies of these messages in the Event Log.

40
Q

reply code actions

A

settings&raquo_space; additional settings

Common to business processes and business operations. Comma-separated list of code-action pairs, specifying which action the business process takes on receipt of various reply status conditions.

Types of reply status condition are identified by a specification code:

E - Error status returned from message handler
E# - Error status returned from message handler has status code equal to
E* - Error status returned from message handler contains text string
X - there is no reply message at all
The following values for may be used alone or in combinations:

C - Treat the message as Completed OK.
W - Log a warning. If no other non-warning are triggered, the message will be treated as Completed OK.
R - Retry the message according to the configured RetryInterval and FailureTimeout; finally Fail unless a different action is also specified.
S - Suspend the message, log an error, and move on to try the next message.
D - Disable the Process, log an error and restore the original incoming message to the front of the Process’s queue.
F - Fail with an error and move on to try the next message from the Process’s queue.

For example:
E#6301=R,E*ErrGeneral=R,E=F
The default value for the Reply Code Actions string is:
E=F

41
Q

Queue Count Alert

A

business process/operation&raquo_space; Settings&raquo_space; Alerting Control

Number of messages on this item’s queue needed to trigger an Alert message to be sent. Note that no further alerts will be sent unless the number of messages on the queue drops below 80% of this number and then rises again to this number.
Note that this alert will be sent even if AlertOnError is False.
Zero means no alerts of this type will be sent.

42
Q

Queue Wait Alert

A

Settings&raquo_space; Alerting Control

Common to business processes and operations.

The number of seconds a message at the front of the queue may have waited since being queued before an alert is triggered.
Only one alert will be raised per host item per sequential trigger of the queue wait threshold.
Note that this alert will be sent even if AlertOnError is False.
Zero means no alerts of this type will be sent.

43
Q

Alert On Error

A

Settings&raquo_space; Alerting Control

Common to all business hosts. When this setting is set to True, as soon as the business host encounters any type of error condition it automatically triggers an alert. An alert writes a message to the Ensemble Event Log and can also send notification to a user via email or pager.

44
Q

Retry Interval

A

business operation&raquo_space; Settings&raquo_space; Additional Settings

Number of seconds to wait between attempts to connect with a destination outside Ensemble.

45
Q

Failure Timeout

A

business operation&raquo_space; Settings&raquo_space; Additional Settings

Total number of seconds to keep trying to connect with a destination outside Ensemble. After this number of seconds has elapsed, the business operation discards the message data and returns an error code. To ensure that no message is ever skipped, enter a Failure Timeout value of –1, which means “never time out.” Use a setting of –1 when complete data delivery is critical, for example in healthcare applications.

46
Q

Open Timeout

A

file business operation&raquo_space; Settings&raquo_space; Additional Settings

Number of seconds to wait on each attempt to open the output file.

47
Q

Overwrite

A

Settings&raquo_space; Additional Settings

Overwrite file if it exists, instead of appending

48
Q

What is a business host?

A

An Ensemble business host is any business service, business process, or business operation within an Ensemble production. These are also referred to generically as configuration items.
A configuration item is always associated with a specific production. It may resemble or duplicate items in other productions. Each production is an entirely closed universe that does not use configuration items from other productions.

49
Q

The purpose of system default settings is to

A

simplify the process of copying a production definition from one environment to another. In any production, the values of some settings are determined as part of the production design; these settings should usually be the same in all environments. Other settings, however, must be adjusted to the environment; these settings include file paths, port numbers, and so on.

To find the value for a setting for a production, business host, or adapter, Ensemble searches the following locations, in order:

  1. The production definition. If Ensemble finds a value for a setting here (even if the value is an empty string), it uses that value.
  2. The system default settings, which are stored outside the production definition.
    If Ensemble finds a value here (even if the value is an empty string), it uses that value.
3. The value of the setting as specified in the definition of the class on which the production, business host, or adapter is based.
Ensemble uses this value only if there is no system default for the setting.
Some settings do not have any default value.

The setting names are color coded as follows:

Black Setting value comes from the production definition — the value you enter and apply in the configuration page.

Green Setting value comes from the class definition; it is the default value for the property as defined in the class.

Blue Setting value comes from the default settings you enter in the Default Settings page for the namespace.

50
Q

What are the elements that define a system default setting?

A

Production Name—Optionally, specifies the production to which this default applies. If set to *, this default applies to all productions in the namespace.

Host Class Name—Optional, specifies the class of the business host to which this default applies. If set to *, this default applies to all hosts in the production or in all productions.

Setting Name—Specifies the name of the property to set. Note that property names do not include spaces. In most cases, the property name is similar to the setting name, with the spaces removed. For example, the setting Log Trace Events is based on a property called LogTraceEvents.

Setting Value—Specifies the value to assign to the property. If this field is blank; it sets the default to an empty string.

Description—Optional, specifies a description of the default.

Deployable—If set, the system default setting can be deployed.

51
Q

The Enterprise Message Bank

A

is an optional remote archiving facility where you can collect messages, Event Log items, and search table entries from multiple Ensemble client productions.

52
Q

Job Per Connection

A

Business Service > Settings > Connection Settings

Spawn a new Job to handle each incoming TCP connection. Allows simultaneous handling of multiple connections.
Note that the performance of this setting can be affected by changing the configured QSize setting of this adapter and by configuring Job Servers as a system configuration option.

53
Q

OS Accept Connection Queue Size

A

TCP Business Service > Settings > Connection Settings

How many incoming connections should the OS hold open on our behalf until we get around to dealing with them?
Set to 0 if only one connection at a time is expected. Set to a large number if many clients will connecting rapidly.

54
Q

Stay Connected

A

Business Service > Settings > Connection Settings

The default value of -1 means to stay permanently connected, even during idle times, and treat a disconnection as an error.
If the value is a positive number, then the adapter will stay connected to the remote system between handling requests until idle for this number of seconds.
A zero value means to disconnect immediately after every input event.

55
Q

Read Timeout

A

TCP Business Service/Operation > Settings > Connection Settings

Number of seconds to wait for each successive incoming TCP read, following receipt of initial data from remote TCP port.

56
Q

Framing

A

Business Service > Settings > Connection Settings

HL7 inbound message framing protocol. The options are:
Flexible: Determine framing style from the content of received data of each message received.
Flexible!: Determine framing style from the content of received data of the first message and require subsequent messages to have that same framing style.
None: No framing - Each line that begins with ‘MSH’ is the start of a new message.
MLLP: Minimal Lower Level Protocol - Frame each HL7 message with ASCII code 11 prefix and ASCII code 28,13 suffix.
MLLPN/M: Minimal Lower Level Protocol - Frame each HL7 message with ASCII code N prefix, and ASCII code M suffix followed by an additional ASCII code 13.
AsciiLF: Frame messages with ASCII code 10 (Line Feed) separating each message from the subsequent one.
AsciiCR: Frame messages with an extra ASCII code 13 (Carriage Return) separating each message from the subsequent one.
AsciiM: Frame messages with ASCII code M suffix character(s) separating each message from the subsequent one.
AsciiN/M: Frame messages with ASCII code N prefix character(s) before each message and ASCII code M suffix character(s), but no trailing ASCII code 13 as in MLLPN/M.
LLP: Lower Level Protocol - (Obsolete) Frame each HL7 message in a redundant checksum block.
Notes:
- ASCII code N is a sequence of one or more characters represented by their ASCII code, separated by comma in case of more than one character.
- All ASCII codes should be given in decimal.
- ASCII code 120 (character ‘x’) is not allowed as a framing character.

57
Q

File Spec

A

Business Service > Basic Settings

Wildcard filename to look for; may be a semicolon-separated list of wildcards.

58
Q

Message Schema Category

A

Business Service > Basic Settings

Category to apply to incoming message types to produce a complete DocType specification.
Combines with the document type Name (MSH:9) to produce a MessageType specification which is then used to look up a MessageStructure/DocType in the MessageTypes section of the given HL7 schema category.

This setting may also contain multiple comma-separated type Names followed by = and then a DocTypeCategory or full DocType value to apply to HL7 messages containing that type Name.

A trailing asterisk (*) at the end of a given partial type Name will match any types with that beginning part.

For example: MessageSchemaCategory=’2.3.1, ADT_*=2.5, BAR_P10=2.4, ORM_O01_6=2.4:RDE_O01’
Note that a DocType assignment may be needed for Validation or SearchTableClass indexing.

59
Q

Which types of HL7 business services have the ACK Mode set to never by default?

A

File

FTP

60
Q

Throttle Delay

A

business service/operation > Settings > Additional Settings

Duration of forced idleness before processing the next message, in milliseconds

61
Q

What would cause an empty value in the Reason field of a rule log entry?

A

If a message did not match the constraint and or condition of any of the rules

62
Q

No Fail While disconnected

A

TCP business operation > settings > additional settings

Suspend counting seconds toward FailureTimeout while disconnected.
Does not apply if FailureTimeout=-1 or StayConnected=0.

HealthShare (10 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2024 Bold Learning Solutions. Terms and Conditions