diff --git a/config.py b/config.py
index 70a191d1c31..62278b0f6d6 100755
--- a/config.py
+++ b/config.py
@@ -20,6 +20,7 @@
 import re
 import os
 import subprocess
+import shutil
 
 # The set of platforms for which this branch supports automated builds
 BUILDBOT_PLATFORM_TRIPLES = (
@@ -788,6 +789,7 @@ def configure_mac(opts):
     validate_target_arch(opts)
     validate_xcode_sdks(opts)
     validate_java_tools(opts)
+    copy_workspace_settings(opts)
 
     args = core_gyp_args(opts) + ['-Dtarget_sdk=' + opts['XCODE_TARGET_SDK'],
                                   '-Dhost_sdk=' + opts['XCODE_HOST_SDK'],
@@ -814,5 +816,23 @@ def configure(args):
     }
     configure_procs[opts['OS']](opts)
 
+def copy_workspace_settings(opts):
+    validate_gyp_settings(opts)
+    if opts['BUILD_EDITION'] == 'commercial':
+        project = os.path.join(opts['GENERATOR_OUTPUT'], '..', 'livecode-commercial.xcodeproj')
+    else:
+        project = os.path.join(opts['GENERATOR_OUTPUT'], 'livecode.xcodeproj')
+
+    xcshareddata = os.path.join(project, 'project.xcworkspace', 'xcshareddata')
+
+    if not os.path.exists(xcshareddata):
+        os.makedirs(xcshareddata)
+
+    workspacesettingsdest= os.path.join(xcshareddata, 'WorkspaceSettings.xcsettings')
+    workspacesettingssource = os.path.join('config', 'WorkspaceSettings.xcsettings')
+
+    if not os.path.exists(workspacesettingsdest):
+        shutil.copyfile(workspacesettingssource, workspacesettingsdest)
+
 if __name__ == '__main__':
     configure(sys.argv[1:])
diff --git a/config/WorkspaceSettings.xcsettings b/config/WorkspaceSettings.xcsettings
new file mode 100644
index 00000000000..f60c042dcf9
--- /dev/null
+++ b/config/WorkspaceSettings.xcsettings
@@ -0,0 +1,8 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
+<plist version="1.0">
+<dict>
+    <key>BuildSystemType</key>
+    <string>Original</string>
+</dict>
+</plist>
\ No newline at end of file
diff --git a/docs/dictionary/command/mobileSetKeyboardType.lcdoc b/docs/dictionary/command/mobileSetKeyboardType.lcdoc
index 296d2a8abbc..3773b6b930e 100644
--- a/docs/dictionary/command/mobileSetKeyboardType.lcdoc
+++ b/docs/dictionary/command/mobileSetKeyboardType.lcdoc
@@ -25,13 +25,15 @@ Parameters:
 type (enum):
 The type of keyboard to use. One of:
 
--   "default": the alphabetic keyboard
+-   "default": the default keyboard
+-   "alphabet": the alphabetic keyboard
 -   "numeric": the numeric keyboard with punctuation
 -   "url": the url entry keyboard (iOS only)
 -   "number": the number pad keyboard
 -   "phone": the phone number pad keyboard
 -   "contact": the phone contact pad keyboard (iOS only)
 -   "email": the email keyboard
+-   "decimal": the decimal numeric pad keyboard
 
 
 Description:
diff --git a/docs/dictionary/command/mobileStoreRestorePurchases.lcdoc b/docs/dictionary/command/mobileStoreRestorePurchases.lcdoc
index f6ac319cec9..1160ab230e2 100644
--- a/docs/dictionary/command/mobileStoreRestorePurchases.lcdoc
+++ b/docs/dictionary/command/mobileStoreRestorePurchases.lcdoc
@@ -42,7 +42,7 @@ pState = "restored"
 > interacting with the Google Play Store in-app purchasing API, where
 > consumables are treated exactly the same way as non-consumables.
 
->*Note:*  : For iOS, non-renewing subscriptions cannot be restored, due
+>*Note:*  For iOS, non-renewing subscriptions cannot be restored, due
 > to technical restrictions imposed by Apple. This means that developers
 > are responsible for restoring non-renewing subscriptions and making
 > them available across all devices the users own.
diff --git a/docs/dictionary/command/modal.lcdoc b/docs/dictionary/command/modal.lcdoc
index 6a9c53fca98..93fee79d596 100644
--- a/docs/dictionary/command/modal.lcdoc
+++ b/docs/dictionary/command/modal.lcdoc
@@ -24,8 +24,8 @@ stack:
 Any stack reference.
 
 Description:
-Use the <modal> <command> to display a <stack> as a custom <modal dialog
-box>. 
+Use the <modal> <command> to display a <stack> as a custom 
+<modal dialog box>. 
 
 >*Important:*  When a <stack> is opened as <modal> its <location> is set
 > to the center of the <defaultStack> if the <defaultStack> is open and
@@ -56,10 +56,10 @@ are sent regardless of the setting of the <lockMessages> <property>.
 If the stack is already displayed as a modal dialog box, the <modal>
 <command> does not close and reopen it.
 
-The <modal> <command> pauses the running <handler> until the <modal
-dialog box> is dismissed (usually by clicking a button in the <modal
-dialog box>). To <return> information to the <handler> about which
-<button(keyword)> was clicked, in the <button(object)|button's>
+The <modal> <command> pauses the running <handler> until the 
+<modal dialog box> is dismissed (usually by clicking a button in the 
+<modal dialog box>). To <return> information to the <handler> about 
+which <button(keyword)> was clicked, in the <button(object)|button's>
 <script>, set a <global|global variable> or <custom property>. After the
 <dialog box> is dismissed, the <handler> can query this <variable> or
 <property> and act accordingly.
@@ -72,7 +72,7 @@ regardless of the current setting of the <tool> <property>.
 References: lock messages (command), ask (command),
 ask file with type (command), modeless (command), return (constant),
 tool (function), variable (glossary), editable window (glossary),
-property (glossary), dialog box (glossary), location (glossary),
+property (glossary), dialog box (glossary), location (property),
 execute (glossary), modal dialog box (glossary), command (glossary),
 global (glossary), Browse tool (glossary), custom property (glossary),
 message (glossary), current card (glossary), handler (glossary),
diff --git a/docs/dictionary/command/modeless.lcdoc b/docs/dictionary/command/modeless.lcdoc
index acff43cb8e1..1c3df3df169 100644
--- a/docs/dictionary/command/modeless.lcdoc
+++ b/docs/dictionary/command/modeless.lcdoc
@@ -24,8 +24,8 @@ stack:
 Any stack reference.
 
 Description:
-Use the <modeless> <command> to display a <stack> as a custom <modeless
-dialog box>.
+Use the <modeless> <command> to display a <stack> as a custom 
+<modeless dialog box>.
 
 A modeless dialog box behaves like an ordinary window, except that it
 cannot be edited. Use modeless dialog boxes to ask the user for
diff --git a/docs/dictionary/command/move.lcdoc b/docs/dictionary/command/move.lcdoc
index 7a615ee0e76..0e35bb30561 100644
--- a/docs/dictionary/command/move.lcdoc
+++ b/docs/dictionary/command/move.lcdoc
@@ -97,7 +97,7 @@ References: drag (command), grab (command), lock moves (command),
 stop moving (command), unlock moves (command), movingControls (function),
 object (glossary), property (glossary), handler (glossary),
 execute (glossary), message (glossary), statement (glossary),
-curve (glossary), command (glossary), without (keyword),
+command (glossary), curve (keyword),  without (keyword),
 graphic (keyword), relative (keyword), moveStopped (message),
 control (object), lockMoves (property), syncRate (property),
 moveSpeed (property), location (property), points (property),
diff --git a/docs/dictionary/command/print.lcdoc b/docs/dictionary/command/print.lcdoc
index 61b9c979d22..7dee006cc18 100644
--- a/docs/dictionary/command/print.lcdoc
+++ b/docs/dictionary/command/print.lcdoc
@@ -8,7 +8,7 @@ Syntax: print {<stack> | <card> |{marked| <number> |all} cards} [into <pageRect>
 
 Syntax: print {<stack> | <card> |{marked| <number> |all} cards} [from <topLeft> to <bottomRight>]
 
-Syntax: print break&gt;
+Syntax: print break
 
 Summary:
 Prints one or more <card|cards>.
@@ -99,12 +99,12 @@ the size of the cards and on whether you specify a <pageRect>.
 The print <marked> cards form prints all the cards in the current stack
 whose <mark> <property> is set to true.
 
-The print all cards form is equivalent to print this stack.
+The print all cards form is equivalent to `print this stack`.
 
 The print break form forces a page break.
 
->*Note:* If a <card(keyword)> is larger than a full page, the <print
-> command> prints only the first page of the <card(keyword)>, starting
+>*Note:* If a <card(keyword)> is larger than a full page, the <print>
+> command prints only the first page of the <card(keyword)>, starting
 > at the top left corner. To print the entire <card(keyword)>, use the
 > <print>...into pageRect form to scale the card to the page.
 
@@ -122,8 +122,7 @@ set the <lockScreen> <property> to true before you print.
 
 References: revPrintReport (command), answer page setup (command),
 mark (command), cancel printing (command), revBrowserPrint (command),
-open printing (command), print command (command),
-close printing (command), answer printer (command),
+open printing (command), close printing (command), answer printer (command),
 reset printing (command), object (glossary), property (glossary),
 Windows (glossary), Unix (glossary), command (glossary),
 PostScript (glossary), Mac OS (glossary), file (keyword),
diff --git a/docs/dictionary/control_st/repeat.lcdoc b/docs/dictionary/control_st/repeat.lcdoc
index eb50e0f7986..bcfe23e87de 100644
--- a/docs/dictionary/control_st/repeat.lcdoc
+++ b/docs/dictionary/control_st/repeat.lcdoc
@@ -242,6 +242,18 @@ during the second, and so on:
         put myLine
     end repeat
 
+>*Note:* The *counterVariable* *myLine* is 0 in the final iteration of
+the loop as it is only once the *counterVariable* is less than or equal 
+to the *endValue* that the loop will perform its final iteration. To
+prevent the loop executing one more iteration than desired, one could 
+compare the two and use <exit repeat> to end the iteration immediately. 
+For example:
+
+    repeat with myLine = 20 to 1 step -2
+        if myLine <= 1 then exit repeat
+        put myLine
+    end repeat
+
 
 >*Note:*  It is possible to change the *counterVariable* in a statement 
 in the loop. However, doing this is not recommended, because it makes 
@@ -313,8 +325,9 @@ variable inside a for each loop without affecting the
 iterations of the loop.
 
 References: wait (command), next repeat (control structure),
-round (function), iteration (glossary), array (glossary),
-chunk (glossary), conditional (glossary), container (glossary),
+exit repeat (control structure), round (function), 
+iteration (glossary), array (glossary), chunk (glossary), 
+conditional (glossary), container (glossary), 
 control structure (glossary), delimit (glossary), element (glossary),
 execute (glossary), field (glossary), function (glossary),
 integer (glossary), keyword (glossary), statement (glossary),
diff --git a/docs/dictionary/function/mobileStoreProductProperty.lcdoc b/docs/dictionary/function/mobileStoreProductProperty.lcdoc
index 15e7234bcb7..b1dbd9813dc 100644
--- a/docs/dictionary/function/mobileStoreProductProperty.lcdoc
+++ b/docs/dictionary/function/mobileStoreProductProperty.lcdoc
@@ -60,7 +60,7 @@ of the purchased product. It should be handled in the
 For Samsung Store (Android), you can query the properties:
 
 - title : title of the item purchased
-- <productId> : identifier of the purchased product
+- productId : identifier of the purchased product
 - price : price of purchased product
 - currencyUnit : currency unit of the product price
 - description : description of the item as specified in Samsung Seller
@@ -77,7 +77,7 @@ For Samsung Store (Android), you can query the properties:
 
 For Google Play Store (Android), you can query the properties :
 
-- <productId> : identifier of the purchased product
+- productId : identifier of the purchased product
 - packageName : application package for which the purchase originated
 - orderId : unique order identifier for the transaction. This
   corresponds to the Google Wallet Order ID
@@ -95,7 +95,7 @@ For Google Play Store (Android), you can query the properties :
 
 For Amazon Store (Android) you can query the properties : 
 
-- <productId> : identifier of the purchased product
+- productId : identifier of the purchased product
 - itemType : type of the purchased item, CONSUMABLE, ENTITLED or
   SUBSCRIPTION 
 - subscriptionPeriod : string indicating the start and end date for
@@ -108,7 +108,7 @@ For iTunes Store (iOS), you can query for the properties:
 
 - quantity : amount of product purchased. You can specify a value for
   this in <mobileStoreMakePurchase>
-- <productId> : identifier of the purchased product
+- productId : identifier of the purchased product
 - receipt : block of data that can be used to confirm the purchase from
   a remote server with the itunes store
 - purchaseDate : date the purchase/restore request was sent
diff --git a/docs/dictionary/function/mouseCharChunk.lcdoc b/docs/dictionary/function/mouseCharChunk.lcdoc
index 84464cc6bcb..92e6d8f20dc 100644
--- a/docs/dictionary/function/mouseCharChunk.lcdoc
+++ b/docs/dictionary/function/mouseCharChunk.lcdoc
@@ -37,10 +37,10 @@ The <mouseCharChunk> <function> only <return|returns> locations in a
 
 The first and second character numbers in the return value are always
 identical, unless the mouse is over a field but there is no text under
-it. In this case, the <mouseCharChunk> <return|returns> a <chunk
-expression> of the form char charNumber to charNumber - 1 of field
-fieldNumber, indicating the start of the <mouseLine>. For example, if
-the mouse is over an empty <field>, the <mouseCharChunk>
+it. In this case, the <mouseCharChunk> <return|returns> a 
+<chunk expression> of the form char charNumber to charNumber - 1 of 
+field fieldNumber, indicating the start of the <mouseLine>. For example, 
+if the mouse is over an empty <field>, the <mouseCharChunk>
 <return|returns> char 1 to 0 of field fieldNumber.
 
 To get the actual character clicked, use the <mouseChar> <function>.
diff --git a/docs/dictionary/function/mouseChunk.lcdoc b/docs/dictionary/function/mouseChunk.lcdoc
index 29357b94af8..e679819ca93 100644
--- a/docs/dictionary/function/mouseChunk.lcdoc
+++ b/docs/dictionary/function/mouseChunk.lcdoc
@@ -37,8 +37,8 @@ The <mouseChunk> <function> only <return|returns> locations in a
 
 The return value reports the word the mouse is over. The startChar is
 the first <character> of the <word>, and the endChar is the last
-<character>. If the <textStyle> of the text is "link", the <return
-value> specifies the entire <grouped text|text group>.
+<character>. If the <textStyle> of the text is "link", the 
+<return value> specifies the entire <grouped text|text group>.
 
 To get the text of the word or text group, use the mouseText <function>.
 
diff --git a/docs/dictionary/function/mouseText.lcdoc b/docs/dictionary/function/mouseText.lcdoc
index e0c270d71ac..03a9fd0a025 100644
--- a/docs/dictionary/function/mouseText.lcdoc
+++ b/docs/dictionary/function/mouseText.lcdoc
@@ -43,11 +43,11 @@ To get the location of the word or text group clicked, use the
 mouseChunk <function>.
 
 >*Important:*  Words are defined a little differently by the <mouseText>
-> <function> than the way they are used in <chunk expression|chunk
-> expressions>. A word, for purposes of the <mouseText>, is any text
-> delimited by spaces, tabs, returns, or punctuation. If the mouse
-> pointer is over a punctuation <character>, only that <character> is
-> returned. 
+> <function> than the way they are used in 
+> <chunk expression|chunk expressions>. A word, for purposes of the 
+> <mouseText>, is any text delimited by spaces, tabs, returns, or 
+> punctuation. If the mouse pointer is over a punctuation <character>, 
+> only that <character> is returned. 
 
 References: function (control structure), clickText (function),
 mouseCharChunk (function), handler (glossary), grouped text (glossary),
diff --git a/docs/dictionary/function/number.lcdoc b/docs/dictionary/function/number.lcdoc
index fb4a79db051..d191bc99c54 100644
--- a/docs/dictionary/function/number.lcdoc
+++ b/docs/dictionary/function/number.lcdoc
@@ -14,6 +14,8 @@ Syntax: the number of [marked] cards [{in | of} <stackRef>]
 
 Syntax: the number of {char[acters] | items | words | lines} {in | of} <textString>
 
+Syntax: the number of elements {in | of} <arrayExpr>
+
 Summary:
 <return|Returns> the number of <object|objects> of a certain kind, or
 the number of <chunk|chunks> in a <string>.
@@ -57,6 +59,9 @@ Any stack reference.
 textString (string):
 Any string or expression that evaluates to a string.
 
+arrayExpr (array):
+Any array or expression that evaluates to an array.
+
 Returns(integer):
 The <number> <function> <return|returns> a <non-negative> <integer>.
 
@@ -99,7 +104,7 @@ function (control structure), length (function), property (glossary),
 current card (glossary), return (glossary), group (glossary),
 nest (glossary), chunk (glossary), read-only (glossary),
 expression (glossary), non-negative (glossary), object (glossary),
-string (keyword), control (keyword), integer (keyword), control (object),
+string (keyword), control (keyword), integer (keyword), stack (object),
 backgroundBehavior (property), layer (property)
 
 Tags: text processing
diff --git a/docs/dictionary/function/revOpenDatabase.lcdoc b/docs/dictionary/function/revOpenDatabase.lcdoc
index aa85083985d..f7c562ec567 100644
--- a/docs/dictionary/function/revOpenDatabase.lcdoc
+++ b/docs/dictionary/function/revOpenDatabase.lcdoc
@@ -114,7 +114,7 @@ cursorType (enum):
 
 
 sqliteOptions (enum):
-A comma delimited list contain one or me of the following (Note that the
+A comma-delimited list containing one or more items listed below (Note 
 order of the items in the options parameter is not important):
 
 -   "extensions": Enable loadable extensions for the connection.
@@ -219,6 +219,14 @@ revOpenDatabase() call when creating the database connection.
 The SQLite revOpenDatabase() call no longer requires 5 arguments and
 only requires a minimum of 2.
 
+>*Important:* To create and/or connect to a SQLite database on Linux,
+> you now need to update GCC to version 4.9. To do this on Ubuntu, 
+> use the following commands in a terminal:
+
+    sudo add-apt-repository ppa:ubuntu-toolchain-r/test
+    sudo apt-get-update
+    sudo apt-get install gcc-.4.9 g++-4.9
+
 The version of the PostgreSQL library has been updated to 9.4.5.
 
 Changes:
diff --git a/docs/dictionary/keyword/modemcolon.lcdoc b/docs/dictionary/keyword/modemcolon.lcdoc
index b05d4ca63d1..c277a71f777 100644
--- a/docs/dictionary/keyword/modemcolon.lcdoc
+++ b/docs/dictionary/keyword/modemcolon.lcdoc
@@ -5,9 +5,9 @@ Type: keyword
 Syntax: modem:
 
 Summary:
-Used with the <open file>, <read from file>, <write to file>, and <close
-file> <command|commands> to specify the modem <port> on <Mac OS|Mac OS
-systems>. 
+Used with the <open file>, <read from file>, <write to file>, and 
+<close file> <command|commands> to specify the modem <port> on 
+<Mac OS|Mac OS systems>. 
 
 Introduced: 1.0
 
@@ -35,13 +35,13 @@ To use the printer port on Mac OS systems, use the printer: <keyword>.
 (To use serial ports other than the built-in printer or modem port, use
 the <open driver> <command>.)
 
-To use serial ports on Windows systems, use the COM1: through <COM9:>
-<keyword|keywords>. 
+To use serial ports on Windows systems, use the <COMn:|COM1:> through 
+<COMn:|COM9:> <keyword|keywords>. 
 
 References: write to file (command), close file (command),
 open file (command), write to driver (command), open driver (command),
 read from file (command), keyword (glossary), property (glossary),
-command (glossary), Mac OS (glossary), port (glossary), COM9: (keyword),
+command (glossary), Mac OS (glossary), port (glossary), COMn: (keyword),
 serialControlString (property)
 
 Tags: networking
diff --git a/docs/dictionary/message/libraryStack.lcdoc b/docs/dictionary/message/libraryStack.lcdoc
index 0d688feb465..e884224994c 100644
--- a/docs/dictionary/message/libraryStack.lcdoc
+++ b/docs/dictionary/message/libraryStack.lcdoc
@@ -5,8 +5,8 @@ Type: message
 Syntax: libraryStack
 
 Summary:
-Sent to a <stack> when it is placed in the <message path> by the <start
-using> <command>.
+Sent to a <stack> when it is placed in the <message path> by the 
+<start using> <command>.
 
 Associations: stack
 
diff --git a/docs/dictionary/message/mouseLeave.lcdoc b/docs/dictionary/message/mouseLeave.lcdoc
index 0c1b9a6de15..44eea4a8a21 100644
--- a/docs/dictionary/message/mouseLeave.lcdoc
+++ b/docs/dictionary/message/mouseLeave.lcdoc
@@ -22,8 +22,8 @@ on mouseLeave -- hide another object
 end mouseLeave
 
 Description:
-Handle the <mouseLeave> <message> to update a <control> when the <mouse
-pointer> moves outside it.
+Handle the <mouseLeave> <message> to update a <control> when the 
+<mouse pointer> moves outside it.
 
 The <mouseLeave> <message> is sent only when the <Browse tool> is being
 used. 
diff --git a/docs/dictionary/message/mouseMove.lcdoc b/docs/dictionary/message/mouseMove.lcdoc
index 6dfd1031b69..ec715cd3e0a 100644
--- a/docs/dictionary/message/mouseMove.lcdoc
+++ b/docs/dictionary/message/mouseMove.lcdoc
@@ -44,10 +44,10 @@ The <parameter|parameters> sent with the <mouseMove> <message> describe
 the <mouse pointer|mouse pointer's> current location.
 
 If the mouse button is down, the <mouseMove> <message> continues to be
-sent to the <object(glossary)> that was clicked, even if the <mouse
-pointer> moves outside that <object(glossary)>. However, if the <mouse
-button> was down at the time the <pointer> entered the <control>, no
-<mouseMove> <message|messages> are sent until the <mouse button> is
+sent to the <object(glossary)> that was clicked, even if the 
+<mouse pointer> moves outside that <object(glossary)>. However, if the 
+<mouse button> was down at the time the <pointer> entered the <control>, 
+no <mouseMove> <message|messages> are sent until the <mouse button> is
 released while the <pointer> is still in the <control>.
 
 References: grab (command), mouseCharChunk (function), object (glossary),
diff --git a/docs/dictionary/message/mouseStillDown.lcdoc b/docs/dictionary/message/mouseStillDown.lcdoc
index 8d93836aecc..c956a768e7f 100644
--- a/docs/dictionary/message/mouseStillDown.lcdoc
+++ b/docs/dictionary/message/mouseStillDown.lcdoc
@@ -34,8 +34,8 @@ The period between <mouseStillDown> <message|messages> is specified by
 the <idleRate> and <idleTicks> <properties>.
 
 The <mouseStillDown> <message> is sent only when the <Browse tool> is
-being used. If an <unlock|unlocked> <field> is clicked with <mouse
-button> 1 or 2, no <mouseStillDown> <message> is sent.
+being used. If an <unlock|unlocked> <field> is clicked with 
+<mouse button> 1 or 2, no <mouseStillDown> <message> is sent.
 
 Usually, it is easier and more efficient to use the <mouseMove> <message>
 to track the movement of the mouse while the <mouse button> is being
diff --git a/docs/dictionary/message/mouseUpInBackdrop.lcdoc b/docs/dictionary/message/mouseUpInBackdrop.lcdoc
index db23e4fd2d3..3cd78293411 100644
--- a/docs/dictionary/message/mouseUpInBackdrop.lcdoc
+++ b/docs/dictionary/message/mouseUpInBackdrop.lcdoc
@@ -5,8 +5,8 @@ Type: message
 Syntax: mouseUpInBackdrop <pButtonNumber>
 
 Summary:
-Sent when the user releases the <mouse button>. while the <mouse
-pointer> is in the backdrop.
+Sent when the user releases the <mouse button>. while the 
+<mouse pointer> is in the backdrop.
 
 Associations: card
 
diff --git a/docs/dictionary/message/mouseWithin.lcdoc b/docs/dictionary/message/mouseWithin.lcdoc
index 9c421c791fc..9c542329e6c 100644
--- a/docs/dictionary/message/mouseWithin.lcdoc
+++ b/docs/dictionary/message/mouseWithin.lcdoc
@@ -36,11 +36,11 @@ receive a <mouseWithin> <message>.
 
 If the mouse button is down when the mouse pointer enters the control,
 no <mouseWithin> <message|messages> are sent until the mouse button is
-released. If the <mouse pointer> leaves the <control> while the <mouse
-button> is still down, no <mouseWithin> <message|messages> are sent. If
-the <mouse button> is pressed while the <pointer> is in the <control>,
-however, <mouseWithin> <message|messages> continue to be sent, even
-while the <mouse button> is down.
+released. If the <mouse pointer> leaves the <control> while the 
+<mouse button> is still down, no <mouseWithin> <message|messages> are 
+sent. If the <mouse button> is pressed while the <pointer> is in the 
+<control>, however, <mouseWithin> <message|messages> continue to be 
+sent, even while the <mouse button> is down.
 
 Usually, it is easier and more efficient to use the mouseMove <message>
 to track the movement of the mouse while the button is being held down.
diff --git a/docs/dictionary/message/nameChanged.lcdoc b/docs/dictionary/message/nameChanged.lcdoc
index d008302c765..8c6b413548e 100644
--- a/docs/dictionary/message/nameChanged.lcdoc
+++ b/docs/dictionary/message/nameChanged.lcdoc
@@ -31,9 +31,9 @@ The object's new name.
 
 Description:
 Handle the <nameChanged> <message> if you want to make updates when an
-<object|object's> <name> is changed. For example, if you have a <popup
-menu> with the names of <stacks>, the <menu> should be updated when a
-<stack|stack's> name changes.
+<object|object's> <name> is changed. For example, if you have a 
+<popup menu> with the names of <stacks>, the <menu> should be updated 
+when a <stack|stack's> name changes.
 
 The actual change is not triggered by the <nameChanged> <message>, so
 <trap|trapping> the <message> and not allowing it to <pass> does not
diff --git a/docs/dictionary/property/multipleHilites.lcdoc b/docs/dictionary/property/multipleHilites.lcdoc
index 88310e50f28..fd2c8f3a741 100644
--- a/docs/dictionary/property/multipleHilites.lcdoc
+++ b/docs/dictionary/property/multipleHilites.lcdoc
@@ -7,8 +7,8 @@ Type: property
 Syntax: set the multipleHilites of <field> to {true | false}
 
 Summary:
-Specifies whether more than one <line> can be <selected> in a <list
-field>. 
+Specifies whether more than one <line> can be <selected> in a 
+<list field>. 
 
 Associations: field
 
@@ -27,8 +27,8 @@ By default, the <multipleHilites> <property> of newly created
 <field(object)|fields> is set to false.
 
 Description:
-Use the <multipleHilites> <property> to control the <behavior> of <list
-field|list fields>.
+Use the <multipleHilites> <property> to control the <behavior> of 
+<list field|list fields>.
 
 If the <multipleHilites> of a <field(keyword)> is set to true, the user
 can <select> more than one line by dragging within the <field(keyword)>,
diff --git a/docs/dictionary/property/name.lcdoc b/docs/dictionary/property/name.lcdoc
index cb038d20352..67340cd01a0 100644
--- a/docs/dictionary/property/name.lcdoc
+++ b/docs/dictionary/property/name.lcdoc
@@ -69,12 +69,13 @@ named "My Button". The <card> also has a <card control|card field> named
     "/Drive/Folder/Stack.rev" 
 
 
->*Important:*  On <OS X|OS X systems>, <standalone
-> application|standalone applications> are stored as <application
-> bundle|application bundles>. A <application bundle|bundle> behaves
-> like a <file> but is actually a <folder>, and the <main stack> of a
-> <standalone application> is inside this <folder>. The <long> name of a
-> stack in an application is the location of the application inside the
+>*Important:*  On <OS X|OS X systems>, 
+> <standalone application|standalone applications> are stored as 
+> <application bundle|application bundles>. A 
+> <application bundle|bundle> behaves like a <file> but is actually a 
+> <folder>, and the <main stack> of a <standalone application> is 
+> inside this <folder>. The <long> name of a stack in an application 
+> is the location of the application inside the 
 > <application bundle|bundle>, not the <application bundle|bundle's>
 > location. For example, if the <bundle'sfile path> is
 > "/Volumes/Disk/MyApp.app/", the <long> name of the application's main
diff --git a/docs/notes-base/breaking_changes.md b/docs/notes-base/breaking_changes.md
index 9362b74d519..35e04cd494e 100755
--- a/docs/notes-base/breaking_changes.md
+++ b/docs/notes-base/breaking_changes.md
@@ -11,17 +11,20 @@ few problems, for example:
 	
 As an attempt to improve this situation, the code that locks messages
 when closing and opening stacks for standalone builds has been removed.
-This means that where previously mainstacks would not receive openStack
-and closeStack messages during standalone build, they now do.
+This means that where previously mainstacks would not receive any of the 
+`(pre)open*` and `close*` messages (e.g. `preOpenStack`, `openStack`, 
+`openCard`, `closeStack` etc) during standalone build, they now do.
 
 If this causes problems for your stack, you can exit from the handler if 
 standalone building is in progress:
 
-	on closeStack
-		if the mode of stack "revStandaloneProgress" > 0 then
-			exit closesStack
-		end if
-	end closeStack
+    on closeStack
+        if the environment is "development" and \
+          there is a stack "revStandaloneProgress" and \
+          the mode of stack "revStandaloneProgress" > 0 then
+            exit closeStack
+        end if
+    end closeStack
 
 ## LiveCode Builder
 
@@ -36,4 +39,4 @@ Using lc-compile tool in LiveCode 9:
 	
 Using lc-compile tool in LiveCode 8:
 	
-	-1^2 = 1
\ No newline at end of file
+	-1^2 = 1
diff --git a/docs/notes/Bugfix-21592.md b/docs/notes/Bugfix-21592.md
new file mode 100644
index 00000000000..f5f53bbcedd
--- /dev/null
+++ b/docs/notes/Bugfix-21592.md
@@ -0,0 +1 @@
+# Corrected several typos in the revOpenDatabase dictionary entry.
diff --git a/docs/notes/bugfix-19670.md b/docs/notes/bugfix-19670.md
new file mode 100644
index 00000000000..58695663e5b
--- /dev/null
+++ b/docs/notes/bugfix-19670.md
@@ -0,0 +1 @@
+# Fix effective working screenrect on Android when status bar is hidden
\ No newline at end of file
diff --git a/docs/notes/bugfix-20193.md b/docs/notes/bugfix-20193.md
new file mode 100644
index 00000000000..42346861cdb
--- /dev/null
+++ b/docs/notes/bugfix-20193.md
@@ -0,0 +1 @@
+# Fix import snapshot from rect causing other applications to lose focus on Windows
diff --git a/docs/notes/bugfix-21104.md b/docs/notes/bugfix-21104.md
new file mode 100644
index 00000000000..2d32af21d9c
--- /dev/null
+++ b/docs/notes/bugfix-21104.md
@@ -0,0 +1 @@
+# Fixed typo in the print dictionary entry
diff --git a/docs/notes/bugfix-21270.md b/docs/notes/bugfix-21270.md
new file mode 100644
index 00000000000..4e7a7d19738
--- /dev/null
+++ b/docs/notes/bugfix-21270.md
@@ -0,0 +1 @@
+# Added systems requirement note to revOpenDatabase
diff --git a/docs/notes/bugfix-21406.md b/docs/notes/bugfix-21406.md
new file mode 100644
index 00000000000..a03a22e69fd
--- /dev/null
+++ b/docs/notes/bugfix-21406.md
@@ -0,0 +1,2 @@
+# Added `alphabetic` to the list of keyboard types in the mobileSetKeyboardType entry
+
diff --git a/docs/notes/bugfix-21436.md b/docs/notes/bugfix-21436.md
new file mode 100644
index 00000000000..70fc73ad66c
--- /dev/null
+++ b/docs/notes/bugfix-21436.md
@@ -0,0 +1 @@
+# Clarified the behaviour of repeat with.
diff --git a/docs/notes/bugfix-21453.md b/docs/notes/bugfix-21453.md
new file mode 100644
index 00000000000..cebb7404775
--- /dev/null
+++ b/docs/notes/bugfix-21453.md
@@ -0,0 +1 @@
+# Fix crash when calling 'open process path/to/app/bundle'
diff --git a/docs/notes/bugfix-21458.md b/docs/notes/bugfix-21458.md
new file mode 100644
index 00000000000..67ad9dbb4ce
--- /dev/null
+++ b/docs/notes/bugfix-21458.md
@@ -0,0 +1 @@
+# Added "the number of elements of array" to the syntax in the entry for the number.
diff --git a/docs/notes/bugfix-21476.md b/docs/notes/bugfix-21476.md
new file mode 100644
index 00000000000..89bcac7782c
--- /dev/null
+++ b/docs/notes/bugfix-21476.md
@@ -0,0 +1 @@
+# Ensure "the extents of tArray" returns empty if the keys of tArray are not integers
diff --git a/docs/notes/bugfix-21491.md b/docs/notes/bugfix-21491.md
new file mode 100644
index 00000000000..546ea8b57e8
--- /dev/null
+++ b/docs/notes/bugfix-21491.md
@@ -0,0 +1 @@
+# Ensure pageRanges and pageHeights return correct results
diff --git a/docs/notes/bugfix-21529.md b/docs/notes/bugfix-21529.md
new file mode 100644
index 00000000000..15bc83ec57e
--- /dev/null
+++ b/docs/notes/bugfix-21529.md
@@ -0,0 +1 @@
+# Fixed typo and incomplete example in Release Notes
diff --git a/docs/notes/bugfix-21532.md b/docs/notes/bugfix-21532.md
new file mode 100644
index 00000000000..55253484f5f
--- /dev/null
+++ b/docs/notes/bugfix-21532.md
@@ -0,0 +1 @@
+# Fix dragData clearing between mouseDown and dragStart
\ No newline at end of file
diff --git a/docs/notes/bugfix-21552.md b/docs/notes/bugfix-21552.md
new file mode 100644
index 00000000000..24f0d81b8f4
--- /dev/null
+++ b/docs/notes/bugfix-21552.md
@@ -0,0 +1 @@
+# Prevent accidental deletion of a file when building a standalone
diff --git a/docs/notes/bugfix-21556.md b/docs/notes/bugfix-21556.md
new file mode 100644
index 00000000000..093010af5b9
--- /dev/null
+++ b/docs/notes/bugfix-21556.md
@@ -0,0 +1 @@
+# Fixed missing text issue in the libraryStack dictionary entry
diff --git a/docs/notes/bugfix-21572.md b/docs/notes/bugfix-21572.md
new file mode 100644
index 00000000000..38e8a58dcb9
--- /dev/null
+++ b/docs/notes/bugfix-21572.md
@@ -0,0 +1 @@
+# Added list of blend modes to CanvasPropertyBlendMode and EffectPropertyBlendMode
diff --git a/docs/notes/bugfix-21595.md b/docs/notes/bugfix-21595.md
new file mode 100644
index 00000000000..ec3b512eccd
--- /dev/null
+++ b/docs/notes/bugfix-21595.md
@@ -0,0 +1 @@
+# Android API 26: allow opening local files with JavaScript on Android Browser 
diff --git a/engine/src/canvas.lcb b/engine/src/canvas.lcb
index fad8d35025c..a50ad6e5aa8 100644
--- a/engine/src/canvas.lcb
+++ b/engine/src/canvas.lcb
@@ -3315,7 +3315,34 @@ Summary:	The blend mode of an effect.
 
 mEffect:		An expression which evaluates to an effect.
 
-Description:	The blend mode of <mEffect> as a string. Can be any one of the standard canvas blend modes.
+Description:	The blend mode of <mEffect> as a string. Can be any one of:
+- clear
+- copy
+- source over
+- source in
+- source out
+- destination over
+- destination in
+- destination out
+- destination atop
+- xor
+- plus darker
+- plus lighter
+- multiply
+- screen
+- overlay
+- darken
+- lighten
+- color dodge
+- color burn
+- soft light
+- hard light
+- difference
+- exclusion
+- hue
+- saturation
+- color
+- luminosity
 
 Example:
 	// Create an effect with blend mode "source over"
@@ -4019,7 +4046,34 @@ Summary:	The current blend mode of a canvas.
 
 mCanvas:		An expression which evaluates to a canvas.
 
-Description:	The blend mode used for drawing operations on <mCanvas> as a string.
+Description:	The blend mode used for drawing operations on <mCanvas> as a string. Can be any one of:
+- clear
+- copy
+- source over
+- source in
+- source out
+- destination over
+- destination in
+- destination out
+- destination atop
+- xor
+- plus darker
+- plus lighter
+- multiply
+- screen
+- overlay
+- darken
+- lighten
+- color edge
+- color burn
+- soft light
+- hard light
+- difference
+- exclusion
+- hue
+- saturation
+- color
+- luminosity
 
 Example:
 	// Use color dodge mode to draw on canvas
diff --git a/engine/src/clipboard.cpp b/engine/src/clipboard.cpp
index 0b7aa1a5b94..72b0848b598 100644
--- a/engine/src/clipboard.cpp
+++ b/engine/src/clipboard.cpp
@@ -254,6 +254,10 @@ bool MCClipboard::AddText(MCStringRef p_string)
 
     AutoLock t_lock(this);
     
+    // Clear contents if the clipboard contains external data
+    if (m_clipboard->IsExternalData())
+        Clear();
+    
     // Clear contents to ensure that the clipboard does not end up
     // containing data from different copy events.
     // i.e. the HTML/RTF representation would be left untouched
@@ -272,12 +276,6 @@ bool MCClipboard::AddText(MCStringRef p_string)
 
 bool MCClipboard::AddTextToItem(MCRawClipboardItem* p_item, MCStringRef p_string)
 {
-    AutoLock t_lock(this);
-    
-    // Clear contents if the clipboard contains external data
-    if (m_clipboard->IsExternalData())
-        Clear();
-    
     // For each text encoding that the underlying clipboard supports, encode the
     // text and add it.
     bool t_success = true;
diff --git a/engine/src/deploy_windows.cpp b/engine/src/deploy_windows.cpp
index 064610ee7c2..505846ddb14 100644
--- a/engine/src/deploy_windows.cpp
+++ b/engine/src/deploy_windows.cpp
@@ -1681,34 +1681,69 @@ Exec_stat MCDeployToWindows(const MCDeployParameters& p_params)
     
 	IMAGE_SECTION_HEADER *t_payload_section, *t_project_section, *t_resource_section;
     t_payload_section = t_project_section = t_resource_section = nil;
+    
+    
 	uint32_t t_section_count;
-	if (t_success)
+    
+    uint32_t t_output_offset = 0;
+    uint32_t t_base_address = 0;
+    
+    bool t_swap_payload = false;
+    if (t_success)
 	{
 		t_section_count = t_nt_header . FileHeader . NumberOfSections;
-		if (!MCStringIsEmpty(p_params . payload))
-			t_payload_section = &t_section_headers[t_section_count - 3];
-		else
-			t_payload_section = nil;
-        
-        if (!t_icons_only)
-            t_project_section = &t_section_headers[t_section_count - 2];
         
-		t_resource_section = &t_section_headers[t_section_count - 1];
-	}
-
+        IMAGE_SECTION_HEADER *t_temp_section;
+        for (uint32_t t_index = 0; t_index < t_section_count; t_index++)
+        {
+            t_temp_section = &t_section_headers[t_index];
+            
+            if (memcmp(t_temp_section -> Name, ".payload", 8) == 0)
+            {
+                t_payload_section = t_temp_section;
+                if (t_output_offset == 0)
+                {
+                    t_output_offset = t_temp_section -> PointerToRawData;
+                    t_base_address = t_temp_section -> VirtualAddress;
+                }
+                else
+                {
+                    // payload is should be third last
+                    t_swap_payload = true;
+                }
+            }
+            else if (memcmp(t_temp_section -> Name, ".project", 8) == 0)
+            {
+                t_project_section = t_temp_section;
+                if (t_output_offset == 0)
+                {
+                    t_output_offset = t_temp_section -> PointerToRawData;
+                    t_base_address = t_temp_section -> VirtualAddress;
+                }
+            }
+            else if (memcmp(t_temp_section -> Name, ".rsrc", 5) == 0)
+            {
+                t_resource_section = t_temp_section;
+                if (t_output_offset == 0)
+                {
+                    t_output_offset = t_temp_section -> PointerToRawData;
+                    t_base_address = t_temp_section -> VirtualAddress;
+                }
+            }
+        }
+    }
+    
 	// Next we check that there are at least two sections, and they are the
 	// right ones.
-	if (t_success &&
-		((MCStringIsEmpty(p_params . payload) && t_section_count < 2) ||
-			(!MCStringIsEmpty(p_params . payload) && t_section_count < 3)))
+	if (t_success && t_section_count < 2)
 		t_success = MCDeployThrow(kMCDeployErrorWindowsMissingSections);
-	if (t_success && memcmp(t_resource_section -> Name, ".rsrc", 6) != 0)
+	if (t_success && t_resource_section == nil)
 		t_success = MCDeployThrow(kMCDeployErrorWindowsNoResourceSection);
-	if (t_success && !t_icons_only && memcmp(t_project_section -> Name, ".project", 8) != 0)
+	if (t_success && !t_icons_only && t_project_section == nil)
 		t_success = MCDeployThrow(kMCDeployErrorWindowsNoProjectSection);
-	if (t_success && t_payload_section != nil && memcmp(t_payload_section -> Name, ".payload", 8) != 0)
+	if (t_success && !MCStringIsEmpty(p_params . payload) && t_payload_section == nil)
 		t_success = MCDeployThrow(kMCDeployErrorWindowsNoPayloadSection);
-
+    
 	// Read in the resources
 	MCWindowsResources t_resources;
 	MCWindowsResourcesInitialize(t_resources);
@@ -1755,35 +1790,49 @@ Exec_stat MCDeployToWindows(const MCDeployParameters& p_params)
 
 	// Write out everything up to the beginning of the payload (if present) else
 	// the project section.
-	uint32_t t_output_offset;
-	t_output_offset = 0;
 	if (t_success)
 	{
-		if (t_icons_only)
-            t_output_offset = t_resource_section -> PointerToRawData;
-        else if (t_payload_section == nil)
-			t_output_offset = t_project_section -> PointerToRawData;
-		else
-			t_output_offset = t_payload_section -> PointerToRawData;
-
 		t_success = MCDeployFileCopy(t_output, 0, t_engine, 0, t_output_offset);
 	}
-
-	// Write out the payload capsule struct (if needed)
-	uint32_t t_payload_size;
-	t_payload_size = 0;
-	if (t_success && t_payload_section != nil)
+    
+    uint32_t t_base_offset = t_output_offset;
+    
+    // Write out the payload capsule struct (if needed)
+	uint32_t t_payload_size = 0;
+    if (t_success && t_payload_section != nil)
 	{
-		t_success = MCDeployWritePayload(p_params, false, t_output, t_output_offset, t_payload_size);
-		if (t_success)
-			t_output_offset += (t_payload_size + 4095) & ~4095;
-	}
+        if (!MCStringIsEmpty(p_params . payload))
+        {
+            t_success = MCDeployWritePayload(p_params, false, t_output, t_output_offset, t_payload_size);
+            if (t_success)
+                t_output_offset += (t_payload_size + 4095) & ~4095;
+        }
+        else
+        {
+            t_success = MCDeployFileCopy(t_output, t_output_offset, t_engine, t_payload_section -> PointerToRawData, t_payload_section -> SizeOfRawData);
+            if (t_success)
+            {
+                t_payload_size = t_payload_section -> SizeOfRawData;
+                t_output_offset += (t_payload_section -> SizeOfRawData + 4095) & ~4095;
+            }
+        }
+    }
 
 	// Write out the project capsule struct
 	uint32_t t_project_size;
 	t_project_size = 0;
-	if (t_success && !t_icons_only)
-		t_success = MCDeployWriteProject(p_params, false, t_output, t_output_offset, t_project_size);
+	if (t_success && t_project_section != nil)
+    {
+        if (!t_icons_only)
+        {
+            t_success = MCDeployWriteProject(p_params, false, t_output, t_output_offset, t_project_size);
+        }
+        else
+        {
+            t_project_size = t_project_section -> SizeOfRawData;
+            t_success = MCDeployFileCopy(t_output, t_output_offset, t_engine, t_project_section -> PointerToRawData, t_project_size);
+        }
+    }
 
 	// Next use the project size to compute the updated header values we need.
 	uint32_t t_optional_header_size, t_optional_header_offset, t_section_headers_offset;
@@ -1813,11 +1862,13 @@ Exec_stat MCDeployToWindows(const MCDeployParameters& p_params)
 		{
 			t_payload_section -> SizeOfRawData = t_payload_section_size;
 			t_payload_section -> Misc . VirtualSize = t_payload_section_size;
+            t_payload_section -> PointerToRawData = t_base_offset;
+            t_payload_section -> VirtualAddress = t_base_address;
 
 			t_project_section -> VirtualAddress = t_payload_section -> VirtualAddress + t_payload_section_size;
 			t_project_section -> PointerToRawData = t_payload_section -> PointerToRawData + t_payload_section_size;
 		}
-
+        
 		// Resize and shift up the project section (if present)
         if (t_project_section != nil)
         {
@@ -1836,11 +1887,18 @@ Exec_stat MCDeployToWindows(const MCDeployParameters& p_params)
 
 		t_resource_section_offset = t_resource_section -> PointerToRawData;
 		t_resource_section_address = t_resource_section -> VirtualAddress;
+        
+        if (t_swap_payload)
+        {
+            IMAGE_SECTION_HEADER t_swap_header = *t_payload_section;
+            t_section_headers[t_section_count - 2] = *t_project_section;
+            t_section_headers[t_section_count - 3] = t_swap_header;
+        }
 
 		// Update the resource data directory entry and the size of image/initialized data
 		t_nt_header . OptionalHeader . SizeOfImage = t_resource_section_address + t_resource_section_size;
-
-		t_nt_header . OptionalHeader . SizeOfInitializedData = 0;
+        
+        t_nt_header . OptionalHeader . SizeOfInitializedData = 0;
 		for(uint32_t i = 0; i < t_section_count; i++)
 			if (t_section_headers[i] . Characteristics & IMAGE_SCN_CNT_INITIALIZED_DATA)
 				t_nt_header . OptionalHeader . SizeOfInitializedData += MCU_max((unsigned)t_section_headers[i] . SizeOfRawData, (unsigned)(t_section_headers[i] . Misc . VirtualSize + 4095) & ~4095);
diff --git a/engine/src/desktop.cpp b/engine/src/desktop.cpp
index b045e35668b..f2c00257d9f 100644
--- a/engine/src/desktop.cpp
+++ b/engine/src/desktop.cpp
@@ -353,7 +353,7 @@ void MCPlatformHandleMouseMove(MCPlatformWindowRef p_window, MCPoint p_location)
 
 void MCPlatformHandleMouseDown(MCPlatformWindowRef p_window, uint32_t p_button, uint32_t p_count)
 {
-	if (((MCScreenDC *)MCscreen) -> isbackdrop(p_window))
+    if (((MCScreenDC *)MCscreen) -> isbackdrop(p_window))
 	{
 		((MCScreenDC *)MCscreen) -> mousedowninbackdrop(p_button, p_count);
 		return;
@@ -392,8 +392,10 @@ void MCPlatformHandleMouseDown(MCPlatformWindowRef p_window, uint32_t p_button,
 				MCdragimageid = 0;
 				MCdragimageoffset . x = 0;
 				MCdragimageoffset . y = 0;
-                MCdragboard->Clear();
-			}
+                // ensure the dragboard is bound correctly
+                MCAutoRefcounted<MCRawClipboard> t_dragboard(MCRawClipboard::CreateSystemDragboard());
+                MCdragboard->Rebind(t_dragboard);
+            }
 			
 			t_target -> mdown(p_button + 1);
 		}
@@ -442,9 +444,6 @@ void MCPlatformHandleMouseUp(MCPlatformWindowRef p_window, uint32_t p_button, ui
 
 void MCPlatformHandleMouseDrag(MCPlatformWindowRef p_window, uint32_t p_button)
 {
-    MCAutoRefcounted<MCRawClipboard> t_dragboard(MCRawClipboard::CreateSystemDragboard());
-    MCdragboard->Rebind(t_dragboard);
-    
     MCdispatcher -> wmdrag(p_window);
 }
 
diff --git a/engine/src/dskmac.cpp b/engine/src/dskmac.cpp
index 62b83add437..008f8147c94 100644
--- a/engine/src/dskmac.cpp
+++ b/engine/src/dskmac.cpp
@@ -5530,7 +5530,7 @@ static void MCS_startprocess_launch(MCNameRef name, MCStringRef docname, Open_mo
 		FSRef launchedapp;
 		inLaunchSpec.numDocs = 0;
 		inLaunchSpec.itemRefs = NULL;
-		if (MCStringGetLength(docname))
+		if (!MCStringIsEmpty(docname))
 		{
 			if (MCS_mac_pathtoref(docname, t_doc_fsref) != noErr)
 			{
@@ -5549,7 +5549,7 @@ static void MCS_startprocess_launch(MCNameRef name, MCStringRef docname, Open_mo
 	}
     
 	errno = connectionInvalid;
-	if (MCStringGetLength(docname))
+	if (!MCStringIsEmpty(docname))
 	{
 		for (i = 0 ; i < MCnprocesses ; i++)
 			if (MCNameIsEqualTo(name, MCprocesses[i].name, kMCStringOptionCompareExact))
diff --git a/engine/src/exec-array.cpp b/engine/src/exec-array.cpp
index d286dfbff3e..c9aac46bd9d 100644
--- a/engine/src/exec-array.cpp
+++ b/engine/src/exec-array.cpp
@@ -970,7 +970,8 @@ bool MCArraysSplitIndexes(MCNameRef p_key, integer_t*& r_indexes, uindex_t& r_co
 			return false;
 		
         MCAutoNumberRef t_number;
-        if (!MCNumberParse(*t_substring, &t_number))
+        
+        if (!MCNumberParseInteger(*t_substring, &t_number))
         {
             if (!t_indexes . Push(0))
 				return false;
@@ -978,7 +979,7 @@ bool MCArraysSplitIndexes(MCNameRef p_key, integer_t*& r_indexes, uindex_t& r_co
             r_all_integers = false;
             break;
         }
-
+        
         if (!t_indexes . Push(MCNumberFetchAsInteger(*t_number)))
 			return false;
 			
diff --git a/engine/src/java/com/runrev/android/Engine.java b/engine/src/java/com/runrev/android/Engine.java
index fe40eb081ab..0c09f010c92 100644
--- a/engine/src/java/com/runrev/android/Engine.java
+++ b/engine/src/java/com/runrev/android/Engine.java
@@ -1218,8 +1218,8 @@ public String getViewportAsString()
 	private Rect getEffectiveWorkarea()
 	{
 		Rect t_workrect = new Rect();
-		getGlobalVisibleRect(t_workrect);
-		return t_workrect;
+        getWindowVisibleDisplayFrame(t_workrect);
+        return t_workrect;
 	}
 
 	public String getEffectiveWorkareaAsString()
diff --git a/engine/src/java/com/runrev/android/libraries/LibBrowser.java b/engine/src/java/com/runrev/android/libraries/LibBrowser.java
index f02fcb19463..1a793b0a8ba 100644
--- a/engine/src/java/com/runrev/android/libraries/LibBrowser.java
+++ b/engine/src/java/com/runrev/android/libraries/LibBrowser.java
@@ -358,6 +358,8 @@ public void onGeolocationPermissionsShowPrompt( String origin,  GeolocationPermi
 		
 		setWebChromeClient(m_chrome_client);
 		getSettings().setJavaScriptEnabled(true);
+        getSettings().setAllowFileAccessFromFileURLs(true);
+        getSettings().setAllowUniversalAccessFromFileURLs(true);
 		getSettings().setGeolocationEnabled(true);
 		getSettings().setDomStorageEnabled(true);
 		getSettings().setPluginState(WebSettings.PluginState.ON);
diff --git a/engine/src/java/com/runrev/android/nativecontrol/BrowserControl.java b/engine/src/java/com/runrev/android/nativecontrol/BrowserControl.java
index 7d85abad3d7..1f9492669c7 100644
--- a/engine/src/java/com/runrev/android/nativecontrol/BrowserControl.java
+++ b/engine/src/java/com/runrev/android/nativecontrol/BrowserControl.java
@@ -322,6 +322,8 @@ public void onGeolocationPermissionsShowPrompt( String origin,  GeolocationPermi
 		};
 		t_view.setWebChromeClient(m_chrome_client);
         t_view.getSettings().setJavaScriptEnabled(true);
+        t_view.getSettings().setAllowFileAccessFromFileURLs(true);
+        t_view.getSettings().setAllowUniversalAccessFromFileURLs(true);
 		t_view.getSettings().setGeolocationEnabled(true);
 		t_view.getSettings().setDomStorageEnabled(true);
         t_view.getSettings().setPluginState(WebSettings.PluginState.ON);
diff --git a/engine/src/paragraf.cpp b/engine/src/paragraf.cpp
index 75db2b562a6..025f3553998 100644
--- a/engine/src/paragraf.cpp
+++ b/engine/src/paragraf.cpp
@@ -3903,7 +3903,7 @@ Boolean MCParagraph::pageheight(uint2 fixedheight, uint2 &theight,
     // SN-2014-09-17: [[ Bug 13462 ]] Added the space above and below each paragraph
     // FG-2014-11-03: [[ Bug 11688 ]] Take all of the top margin into account
     if (attrs != nil)
-        theight -= computetopmargin();
+        theight = MCU_max(((int32_t)theight) - computetopmargin(), 0);
     
 	do
 	{
@@ -3943,7 +3943,7 @@ Boolean MCParagraph::pagerange(uint2 fixedheight, uint2 &theight,
     
     // FG-2014-11-03: [[ Bug 11688 ]] Take all of the top margin into account
     if (attrs != nil)
-        theight -= computetopmargin();
+        theight = MCU_max(((int32_t)theight) - computetopmargin(), 0);
     
 	do
 	{
diff --git a/engine/src/w32dcs.cpp b/engine/src/w32dcs.cpp
index 9145d818bcd..210b3533e9d 100644
--- a/engine/src/w32dcs.cpp
+++ b/engine/src/w32dcs.cpp
@@ -880,7 +880,14 @@ MCImageBitmap *MCScreenDC::snapshot(MCRectangle &r, uint4 window, MCStringRef di
 	MCRectangle t_device_viewport;
 	t_device_viewport = logicaltoscreenrect(t_virtual_viewport);
 
-	HWND hwndsnap = CreateWindowExA(WS_EX_TRANSPARENT | WS_EX_TOPMOST,
+	DWORD t_ex_options = WS_EX_TRANSPARENT | WS_EX_TOPMOST;
+	// use layered if we don't need to select the snapshot area via cursor
+	if (window != 0 || r.x != -32768)
+	{
+		t_ex_options |= WS_EX_LAYERED;
+	}
+
+	HWND hwndsnap = CreateWindowExA(t_ex_options,
 	                               MC_SNAPSHOT_WIN_CLASS_NAME,"", WS_POPUP, t_device_viewport . x, t_device_viewport . y,
 	                               t_device_viewport . width, t_device_viewport . height, invisiblehwnd,
 	                               NULL, MChInst, NULL);
diff --git a/extensions/widgets/treeview/notes/21567.md b/extensions/widgets/treeview/notes/21567.md
new file mode 100644
index 00000000000..d07b499a275
--- /dev/null
+++ b/extensions/widgets/treeview/notes/21567.md
@@ -0,0 +1 @@
+# [21567] Prevent error when hilitedElement set to empty
\ No newline at end of file
diff --git a/extensions/widgets/treeview/treeview.lcb b/extensions/widgets/treeview/treeview.lcb
index 646c93caec9..6f63467e4c9 100644
--- a/extensions/widgets/treeview/treeview.lcb
+++ b/extensions/widgets/treeview/treeview.lcb
@@ -117,8 +117,9 @@ Description:
 <pPath> is a list of the keys which determine the row to be selected. For example, if tArray is the arrayData
 of the widget, to select a row corresponding to tArray["key1"]["subkey2"]["subsubkey5"], simply execute
 
-
 ``` set the hilitedElement of widget "Array Viewer" to "key1,subkey2,subsubkey5" ```
+
+Setting to an invalid path or to `empty` will unselect the currently selected row.
 **/
 
 property hilitedElement			get getSelectedElement			set setSelectedElement
@@ -1703,21 +1704,27 @@ private handler selectPath(in pPath as List)
 	variable tPathNotAlreadySelected as Boolean
 	put mSelectedElement is not pPath into tPathNotAlreadySelected
 	
+	variable tSelectedElement as optional List
+	put mSelectedElement into tSelectedElement
+
 	// Unselect the existing selection if applicable
 	if mSelectedElement is not nothing and tPathNotAlreadySelected then
 		applyToNode(unselectKey, mSelectedElement, 0, 1, mDataList, mData)
 	end if
 
 	if mSelectedElement is nothing or tPathNotAlreadySelected or \
-			mScrollHilitedElementIntoView then
-		if not applyToNode(selectKey, pPath, 0, 1, mDataList, mData) then
-			put nothing into mSelectedElement
-		end if
-		if tPathNotAlreadySelected then
-			post "hiliteChanged"
-		end if
-		redraw all
+         mScrollHilitedElementIntoView then
+      if pPath is not the empty list and \
+            not applyToNode(selectKey, pPath, 0, 1, mDataList, mData) then
+         put nothing into mSelectedElement
+      end if
+      if tPathNotAlreadySelected then
+         post "hiliteChanged"
+      end if
+      redraw all
 	end if
+		
+	
 end handler
 
 // Unselect the key at the target path
@@ -1737,7 +1744,7 @@ end handler
 private handler applyToNode(in pHandler as NodeApply, in pPathToNode as List, in pLevel as Integer, in pStart as Integer, inout xList as List, inout xArray as Array) returns Boolean	
 	if pStart >= the number of elements in xList then
 		return false
-	end if	
+	end if
 
 	variable tKey as String
 	put element pLevel + 1 of pPathToNode into tKey
diff --git a/ide-support/revsaveasstandalone.livecodescript b/ide-support/revsaveasstandalone.livecodescript
index ffdb9712052..2a61b842479 100644
--- a/ide-support/revsaveasstandalone.livecodescript
+++ b/ide-support/revsaveasstandalone.livecodescript
@@ -312,6 +312,9 @@ command revDoSaveAsStandalone pStack, pFolder, pSettings, @xStandalonePaths
       put the result into tOutputFolder
       if there is no folder tOutputFolder then
          create folder tOutputFolder
+         if the result is not empty then
+            throw format("Cannot create a folder '%s'", tOutputFolder)
+         end if        
       end if
       
       local tBuildPlatforms, tPlatform
@@ -1120,9 +1123,11 @@ end restoreStackToMessagePath
 private command revOutputDirectories pFolder
    local tTarget,tDirectory,tPlatforms,tCount,tOSXCount
    revStandaloneProgress "Checking directories..."
-   if there is a folder (pFolder & sStandaloneSettingsA["name"]) then
+   if there is a folder (pFolder & sStandaloneSettingsA["name"]) or \
+         there is a file (pFolder & sStandaloneSettingsA["name"]) then
       put 1 into tCount
-      repeat while there is a folder (pFolder & sStandaloneSettingsA["name"]&tCount)
+      repeat while there is a folder (pFolder & sStandaloneSettingsA["name"]&tCount) or \
+            there is a file (pFolder & sStandaloneSettingsA["name"]&tCount)
          add 1 to tCount
       end repeat
    end if
diff --git a/libfoundation/include/foundation.h b/libfoundation/include/foundation.h
index c1a8e7f1219..e7855a13f98 100755
--- a/libfoundation/include/foundation.h
+++ b/libfoundation/include/foundation.h
@@ -2053,6 +2053,7 @@ MC_DLLEXPORT bool MCNumberParseOffsetPartial(MCStringRef p_string, uindex_t offs
 
 MC_DLLEXPORT bool MCNumberParseOffset(MCStringRef p_string, uindex_t offset, uindex_t char_count, MCNumberRef &r_number);
 MC_DLLEXPORT bool MCNumberParse(MCStringRef string, MCNumberRef& r_number);
+MC_DLLEXPORT bool MCNumberParseInteger(MCStringRef string, MCNumberRef& r_number);
 MC_DLLEXPORT bool MCNumberParseUnicodeChars(const unichar_t *chars, uindex_t char_count, MCNumberRef& r_number);
     
 #if defined(__HAS_CORE_FOUNDATION__)
diff --git a/libfoundation/src/foundation-number.cpp b/libfoundation/src/foundation-number.cpp
index 65ceb1b8d39..671260ec8cf 100644
--- a/libfoundation/src/foundation-number.cpp
+++ b/libfoundation/src/foundation-number.cpp
@@ -23,6 +23,14 @@ along with LiveCode.  If not see <http://www.gnu.org/licenses/>.  */
 
 ////////////////////////////////////////////////////////////////////////////////
 
+// Forward declarations of internal utility functions
+
+static bool __MCNumberParseNativeString(const char *p_string, uindex_t p_length, bool p_full_string, bool p_integer_only, uindex_t &r_length_used, MCNumberRef &r_number);
+static bool __MCNumberParseOffset(MCStringRef p_string, uindex_t offset, uindex_t char_count, bool p_integer_only, MCNumberRef &r_number);
+static bool __MCNumberParseUnicodeChars(const unichar_t *p_chars, uindex_t p_char_count, bool p_integer_only, MCNumberRef& r_number);
+
+////////////////////////////////////////////////////////////////////////////////
+
 MC_DLLEXPORT_DEF
 bool MCNumberCreateWithInteger(integer_t p_value, MCNumberRef& r_number)
 {
@@ -126,31 +134,101 @@ compare_t MCNumberCompareTo(MCNumberRef self, MCNumberRef p_other_self)
 	return 0;
 }
 
-bool __MCNumberParseNativeString(const char *p_string, uindex_t p_length, bool p_full_string, uindex_t &r_length_used, MCNumberRef &r_number)
+/////////////////////////////////////////////////////////////////////////////////
+
+MC_DLLEXPORT_DEF
+bool MCNumberParseOffset(MCStringRef p_string, uindex_t offset, uindex_t char_count, MCNumberRef &r_number)
+{
+    return __MCNumberParseOffset(p_string, offset, char_count, false, r_number);
+}
+
+MC_DLLEXPORT_DEF
+bool MCNumberParse(MCStringRef p_string, MCNumberRef &r_number)
+{
+    return __MCNumberParseOffset(p_string, 0, MCStringGetLength(p_string), false, r_number);
+}
+
+MC_DLLEXPORT_DEF
+bool MCNumberParseInteger(MCStringRef p_string, MCNumberRef &r_number)
+{
+    return __MCNumberParseOffset(p_string, 0, MCStringGetLength(p_string), true, r_number);
+}
+
+MC_DLLEXPORT_DEF
+bool MCNumberParseUnicodeChars(const unichar_t *p_chars, uindex_t p_char_count, MCNumberRef& r_number)
+{
+    return __MCNumberParseUnicodeChars(p_chars, p_char_count, false, r_number);
+}
+
+MC_DLLEXPORT_DEF
+bool MCNumberParseOffsetPartial(MCStringRef p_string, uindex_t offset, uindex_t &r_chars_used, MCNumberRef &r_number)
 {
 	bool t_success;
 	t_success = true;
 	
-	MCNumberRef t_number;
-	t_number = nil;
+	char *t_buffer;
+	t_buffer = nil;
+	
+	const char *t_native_string;
+	t_native_string = nil;
+	
+	uindex_t t_length;
+	t_length = MCStringGetLength(p_string);
+	
+	if (offset > t_length)
+		offset = t_length;
 	
+	if (MCStringIsNative(p_string))
+		t_native_string = (const char*)MCStringGetNativeCharPtr(p_string) + offset;
+	else
+	{
+		t_success = MCMemoryNewArray(t_length - offset + 1, t_buffer);
+		
+		uindex_t t_native_char_count;
+		if (t_success)
+			t_success = MCUnicodeCharsMapToNative(MCStringGetCharPtr(p_string) + offset, t_length - offset, (char_t*)t_buffer, t_native_char_count, '?');
+
+		t_native_string = t_buffer;
+	}
+	
+	if (t_success)
+		t_success = __MCNumberParseNativeString(t_native_string, t_length - offset, false, false, r_chars_used, r_number);
+	
+	MCMemoryDeleteArray(t_buffer);
+	
+	return t_success;
+}
+
+////////////////////////////////////////////////////////////////////////////////
+
+static bool __MCNumberParseNativeString(const char *p_string, uindex_t p_length, bool p_full_string, bool p_integer_only, uindex_t &r_length_used, MCNumberRef &r_number)
+{
+    bool t_success;
+    t_success = true;
+    
+    MCNumberRef t_number;
+    t_number = nil;
+    
     uinteger_t t_base;
     t_base = 10;
     
     const char *t_string;
     t_string = p_string;
     
-	if (p_length > 2 &&
-		p_string[0] == '0' &&
-		(p_string[1] == 'x' || p_string[1] == 'X'))
-	{
-        // If the string begins with 0x then parse as hex, and discard first two chars
-        t_base = 16;
-        t_string += 2;
+    if (!p_integer_only)
+    {
+        if (p_length > 2 &&
+            p_string[0] == '0' &&
+            (p_string[1] == 'x' || p_string[1] == 'X'))
+        {
+            // If the string begins with 0x then parse as hex, and discard first two chars
+            t_base = 16;
+            t_string += 2;
+        }
     }
     
     errno = 0;
-
+    
     char *t_end;
     t_end  = nil;
     
@@ -166,13 +244,17 @@ bool __MCNumberParseNativeString(const char *p_string, uindex_t p_length, bool p
 #endif
     
     t_success = (errno != ERANGE) && (p_full_string ? (t_end - p_string == (ptrdiff_t)p_length) : (t_end != t_string));
+    
+    if (!t_success && p_integer_only)
+        return false;
+    
     if (t_success)
         t_success = MCNumberCreateWithInteger(t_integer, t_number);
     // If parsing as base 10 unsigned integer failed, try to parse as real.
     else if (t_base == 10)
     {
         errno = 0;
-
+        
         real64_t t_real;
         t_real = strtod(p_string, &t_end);
         
@@ -181,18 +263,17 @@ bool __MCNumberParseNativeString(const char *p_string, uindex_t p_length, bool p
         if (t_success)
             t_success = MCNumberCreateWithReal(t_real, t_number);
     }
-	
-	if (t_success)
-	{
-		r_number = t_number;
-		r_length_used = t_end - p_string;
-	}
-	
-	return t_success;
+    
+    if (t_success)
+    {
+        r_number = t_number;
+        r_length_used = t_end - p_string;
+    }
+    
+    return t_success;
 }
 
-MC_DLLEXPORT_DEF
-bool MCNumberParseOffset(MCStringRef p_string, uindex_t offset, uindex_t char_count, MCNumberRef &r_number)
+static bool __MCNumberParseOffset(MCStringRef p_string, uindex_t offset, uindex_t char_count, bool p_integer_only, MCNumberRef &r_number)
 {
     uindex_t length = MCStringGetLength(p_string);
     if (offset > length)
@@ -207,83 +288,37 @@ bool MCNumberParseOffset(MCStringRef p_string, uindex_t offset, uindex_t char_co
     bool t_success;
     t_success = false;
     
-	uindex_t t_length_used;
-	t_length_used = 0;
-	
-	t_success = __MCNumberParseNativeString((const char*)MCStringGetNativeCharPtr(p_string) + offset, char_count, true, t_length_used, r_number);
-	
-	return t_success;
-}
-
-MC_DLLEXPORT_DEF
-bool MCNumberParse(MCStringRef p_string, MCNumberRef &r_number)
-{
-    return MCNumberParseOffset(p_string, 0, MCStringGetLength(p_string), r_number);
+    uindex_t t_length_used;
+    t_length_used = 0;
+    
+    t_success = __MCNumberParseNativeString((const char*)MCStringGetNativeCharPtr(p_string) + offset, char_count, true, p_integer_only, t_length_used, r_number);
+    
+    return t_success;
 }
 
-MC_DLLEXPORT_DEF
-bool MCNumberParseUnicodeChars(const unichar_t *p_chars, uindex_t p_char_count, MCNumberRef& r_number)
+static bool __MCNumberParseUnicodeChars(const unichar_t *p_chars, uindex_t p_char_count, bool p_integer_only, MCNumberRef& r_number)
 {
-	char *t_native_chars;
-	if (!MCMemoryNewArray(p_char_count + 1, t_native_chars))
-		return false;
+    char *t_native_chars;
+    if (!MCMemoryNewArray(p_char_count + 1, t_native_chars))
+        return false;
     
-	uindex_t t_native_char_count;
-	MCUnicodeCharsMapToNative(p_chars, p_char_count, (char_t *)t_native_chars, t_native_char_count, '?');
+    uindex_t t_native_char_count;
+    MCUnicodeCharsMapToNative(p_chars, p_char_count, (char_t *)t_native_chars, t_native_char_count, '?');
     
-	bool t_success;
-	t_success = false;
-	
-	uindex_t t_length_used;
-	t_length_used = 0;
-	
-	t_success = __MCNumberParseNativeString(t_native_chars, p_char_count, true, t_length_used, r_number);
+    bool t_success;
+    t_success = false;
     
-	MCMemoryDeleteArray(t_native_chars);
+    uindex_t t_length_used;
+    t_length_used = 0;
     
-	return t_success;
-}
-
-MC_DLLEXPORT_DEF
-bool MCNumberParseOffsetPartial(MCStringRef p_string, uindex_t offset, uindex_t &r_chars_used, MCNumberRef &r_number)
-{
-	bool t_success;
-	t_success = true;
-	
-	char *t_buffer;
-	t_buffer = nil;
-	
-	const char *t_native_string;
-	t_native_string = nil;
-	
-	uindex_t t_length;
-	t_length = MCStringGetLength(p_string);
-	
-	if (offset > t_length)
-		offset = t_length;
-	
-	if (MCStringIsNative(p_string))
-		t_native_string = (const char*)MCStringGetNativeCharPtr(p_string) + offset;
-	else
-	{
-		t_success = MCMemoryNewArray(t_length - offset + 1, t_buffer);
-		
-		uindex_t t_native_char_count;
-		if (t_success)
-			t_success = MCUnicodeCharsMapToNative(MCStringGetCharPtr(p_string) + offset, t_length - offset, (char_t*)t_buffer, t_native_char_count, '?');
-
-		t_native_string = t_buffer;
-	}
-	
-	if (t_success)
-		t_success = __MCNumberParseNativeString(t_native_string, t_length - offset, false, r_chars_used, r_number);
-	
-	MCMemoryDeleteArray(t_buffer);
-	
-	return t_success;
+    t_success = __MCNumberParseNativeString(t_native_chars, p_char_count, true, p_integer_only, t_length_used, r_number);
+    
+    MCMemoryDeleteArray(t_native_chars);
+    
+    return t_success;
 }
 
-////////////////////////////////////////////////////////////////////////////////
+////////////////////////////////////////////////////////////////////////////////////////////////
 
 bool __MCNumberCopyDescription(__MCNumber *self, MCStringRef& r_string)
 {
diff --git a/libgraphics/src/drawing.cpp b/libgraphics/src/drawing.cpp
index 8a1d9168392..8739bd10b4e 100644
--- a/libgraphics/src/drawing.cpp
+++ b/libgraphics/src/drawing.cpp
@@ -1731,13 +1731,13 @@ void MCGDrawingContext::ExecutePath(VisitorT& p_visitor)
                 
             case kMCGDrawingPathOpcodeSmoothCubicTo:
             {
-                MCGPoint t_a, t_b, t_point;
-                if (!Point(t_b) ||
+                MCGPoint t_a, t_point;
+                if (!Point(t_a) ||
                     !Point(t_point))
                 {
                     break;
                 }
-                p_visitor.PathSmoothCubicTo(t_b,
+                p_visitor.PathSmoothCubicTo(t_a,
                                             t_point);
             }
             break;
diff --git a/tests/ide-support/standalonebuilder/_support.livecodescript b/tests/ide-support/standalonebuilder/_support.livecodescript
index 522da79cd59..6f35c079019 100644
--- a/tests/ide-support/standalonebuilder/_support.livecodescript
+++ b/tests/ide-support/standalonebuilder/_support.livecodescript
@@ -42,7 +42,10 @@ function GetBuildPlatform
 end GetBuildPlatform
 
 private function GetTargetFolder
-	return TestGetIDERepositoryPath() & "/_tests/_build"
+	local tFolder
+	put TestGetIDERepositoryPath() & "/_tests/_build" into tFolder
+	revSBEnsureFolder tFolder
+	return tFolder
 end GetTargetFolder
 
 on StandaloneBuilderCleanupStandalones 
diff --git a/tests/lcs/core/array/array.livecodescript b/tests/lcs/core/array/array.livecodescript
index 9721efab32e..a597ba9de2a 100644
--- a/tests/lcs/core/array/array.livecodescript
+++ b/tests/lcs/core/array/array.livecodescript
@@ -113,6 +113,25 @@ on TestExtents
    TestAssert "Extents of dimensional arrays", the extents of tDimensionalArray is tExpectedExtents
 end TestExtents
 
+on TestExtentsDecimal
+   local tArray
+   repeat with i=1 to 5
+      put "true" into tArray[i]
+   end repeat
+   put "false" into tArray[1.0]
+   
+   TestAssert "Extents of array with a decimal key", the extents of tArray is empty
+   
+   delete variable tArray[1.0]
+   local tSequenceKeys
+   put __keysForArray(kSequenceArray) into tSequenceKeys
+   TestAssert "Extents of array without a decimal key", the extents of tArray is (item 1 of tSequenceKeys, item -1 of tSequenceKeys)
+   
+   put "false" into tArray[pi]
+   TestAssert "Extents of array with another decimal key", the extents of tArray is empty
+   
+end TestExtentsDecimal
+
 on __testIsAmong pUseIsAmong
    local tArray, tKeyList, tKeys
    
diff --git a/tests/lcs/core/field/_pageHeightsFieldContent.txt b/tests/lcs/core/field/_pageHeightsFieldContent.txt
new file mode 100644
index 00000000000..19d263d0df7
--- /dev/null
+++ b/tests/lcs/core/field/_pageHeightsFieldContent.txt
@@ -0,0 +1,442 @@
+<p spaceabove="5" spacebelow="5"><u><font face="Arial" size="12">Interviewee: 530 PCP, Nurse Practitioner</font></u></p>
+<p></p>
+<p spaceabove="5" spacebelow="5"><u><font face="Arial" size="12">PowerPoint Comments</font></u></p>
+<ul type="disc">
+<li value="1"><p leftindent="27"><font face="Arial" size="12" color="#1F3864">Does not remember going through any kind of training for the CV Wizard</font></p>
+</li>
+</ul><p spaceabove="5" spacebelow="5"></p>
+<p spaceabove="5" spacebelow="5"><u><font face="Arial" size="12">Transcription results:</font></u></p>
+<p></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Melissa (M) 00:01</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Okay, so you mentioned you don't remember the-- or you don't know of the training for the CV Wizard?</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Interviewee (I) 00:06</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I don't recall getting anything specifically, no.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 00:09</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Okay. So how did you start using it? What did you think when you first saw it?</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 00:14</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">There was some discussion from the nurses down the hallway who had-- I think they had received some training in terms of they were going to be the ones who were going to see the notification and then as they were rooming the patient, print off the information. And then from there, I took a look at a couple of the samples and then just incorporated the information into patient education during the visit from there.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 00:36</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Okay. That's good.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">H 00:39</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Would you have liked to have received some sort of formal training or I guess been notified more so of a formal training for the Wizard?</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 00:51</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I guess that would depend on what the goals of the Wizard were. I mean, my understanding of it is it's a way to consolidate those cardiovascular risk factors in one kind of condensed piece of information, so that it's both to my-- brings it to my attention as well as then I can discuss it with the patient at the time. So I mean, if that was the ultimate end, then I would say it's been accomplished [laughter].</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">H 01:18</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Good to know.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 01:19</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">So I don't know what other information there was or could have been that I would have received through the course of instruction.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">H 01:26</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">That's good to know.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 01:27</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">So had you heard which populations it was targeting or--? [interviewee shakes head no] Okay. So that's interesting. So--</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 01:32</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">No [laughter].</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 01:34</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Yeah, so did you--?</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 01:34</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I suppose you can't see my head shaking on the--</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 01:36</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">No. Yeah [laughter].</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 01:37</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I mean, I presumed it was peripheral vascular&nbsp;disease, cardiovascular disease, hypertension, dyslipidemia, I mean, prediabetes, those kinds of--</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 01:44</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Right. Yeah. So what this does is it fires for patients who are prediabetic, diabetic, or have serious mental illness. So other patients who don't have those three&mdash;or don't fall into those categories, it doesn't fire for them. So that's--</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 01:55</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Gotcha.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 01:56</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Yeah. So it's--</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 01:58</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Does it fire for prediabetes based only on laboratory values or based on the ICD-10 code in the problem list?</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 02:05</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I think it might-- it would probably-- it would go on both, I believe, because it's--</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">H 02:09</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I believe it's both, as well.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 02:11</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Yeah. If someone's already been diagnosed with prediabetes, but it also can flag people who are potentially prediabetic--</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 02:18</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">If they've had an A1C checked.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 02:20</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">If they've had an A1C. Exactly. Right. Yeah.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 02:22</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Yeah. Because it doesn't go off of glucose readings, I'm sure.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 02:24</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">No. Yeah. We have the fasting glucose and then the non-fasting and I don't think the EMR differentiates.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 02:33</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Not at all.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 02:33</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Yeah.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 02:33</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Okay.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 02:34</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Okay, so if you had training, what would you think would be the best way for it to be conducted?</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 02:45</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">[laughter] For the CV Wizard or for the--?</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 02:48</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Yes. And the cancer integration into the CV Wizard. What kind of training would you like to see if you had a choice?</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 03:04</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">[pause] I guess I'm finding myself somewhat agnostic on the question. I mean, whether it was face-to-face, I mean, that would be time out of the day. I mean, the SABA training seemed very effective in terms of utilization of this type of a piece. I mean, it depends on, I guess, how broad you would want your intervention to be. If it was just a matter of recognizing the BPA, acknowledging it, and getting the document printed off, it sounds like the LPNs and nurses or medical assistants are going to be utilizing that piece. But if the intervention is primarily focused on utilization of the decision aids, then I would say they probably need some face-to-face support. And how to make that a practical implementation and change into a clinic visit.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 03:51</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Okay.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">H 03:51</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Definitely.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 03:52</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">That's a great answer. So then, prior to our presentation, where have you heard about the cardiovascular Wizard? You mentioned you use it, right?</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 04:02</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Right.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 04:03</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Okay. Have you heard any other talk about it from other physicians at other clinics or other providers, nurse practitioners, and physician assistants?</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 04:11</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Not that it's been-- no, I haven't&nbsp;had conversation with anybody else about it.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 04:14</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Okay. So how do you like it?</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 04:18</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I think it's a helpful tool in terms of-- I mean, there are&nbsp;clinical components and with respect to cardiovascular risk that I feel like I'm discussing with the patients that I'm seeing already, anyway. But to have something tangible and visual that summarizes, I think, the information in a very helpful way provides a tool for pulling that information together, even prioritizing which cardiovascular risk factors to focus on.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 04:49</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Okay. So do you have any concerns about it?</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 04:56</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Not especially. No.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 04:59</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Okay. That's good. Can you think of anything that could make it better?</font></p>
+<p leftindent="26" rightindent="4"></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">[silence]</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 05:15</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Not at this time. No.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 05:16</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Okay. Yeah, that's good feedback. So what are your initial thoughts on a single Wizard that assesses both patients' cardiovascular risk and their cancer prevention screening needs?</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 05:27</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I think as long as the design and utilization is efficient and helpful, I think the aspiration is laudable&nbsp;in terms-- because you're pulling a lot of different pieces that, in the course of a busy day, could easily be overlooked. So if there is that type of a kind of a quick way that pulls all those disparate&nbsp;elements together and summarizes them and says, "We need to address this, this, and this," then I think that's helpful.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 06:02</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Great. And how about integrating it into the clinic work flow?</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 06:08</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">The notification process I would see as being much easier to implement into the clinic work flow because then, I mean, that's flagging, as we discussed before, cervical cancer screening, HPV, all of those different elements. Decision tools, I think, are more labor intensive and demand more time, not just because of the specific components in terms of risks and benefits, but because they have kind of such a separate-- they demand a separate level of focus that rather than having a conversation about it, you really have to kind of carve out a specific amount of time to navigate in and through those. And if you don't utilize them on a regular basis, it becomes even more time intensive. And so I would see that would be the larger barrier of the intervention, would be utilizing those decision aids.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 07:08</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Okay. So it sounds like there's some time considerations that [crosstalk] have time.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 07:11</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Absolutely.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 07:12</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Okay. So how would you prioritize cardiovascular risk and cancer screening with your patients?</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 07:22</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I'm afraid I don't understand the question.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 07:24</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">So say you have a patient that comes in and has cardiovascular risk that's high and they also are due for a cancer prevention screening. How would you prioritize those two needs for that patient?</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 07:37</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I would make the time to address all of them.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 07:40</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Okay. That's great. So in terms of cancer prevention, how does the Wizard compare to other EPIC tools that Essentia Health uses in primary care?</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 07:51</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">From the presentation that I've seen, and not having actually manipulated it in the practice setting, it looks like it functions in much the same way as other tools that we already have in terms of BPAs, specifically.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 08:06</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Okay. And one thing I didn't mention in the presentation is that the Wizard is going to be available both as print copies and then also through EPIC, so you can-- there's a way to fire it currently now, the CV wizard in EPIC. But when it's on the computer, it's in EPIC, there's going to be hyperlinks called active guidelines that will link out to orders. It'll be specific to your clinic.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 08:31</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Order sets or--? Because right now the HPV BPA fires to, I mean, to a reference material that describes kind of the two different, two dose or three dose, but doesn't have an order set in it. In a separate area, it pulls in the smart set under adult immunizations.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 08:49</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Okay. So what this will do, it'll populate orders. So the current BPAs don't do that?</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 08:55</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">They do.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 08:55</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Oh, they do that, too? Okay. So this will put it all on one page, I guess, so online if you want to use it. Otherwise, you can order them the way you're used to ordering stuff, too.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 09:06</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Sure. Yeah.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 09:07</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">So do you see any advantages&nbsp;to this Wizard versus the current EPIC tools?</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 09:17</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I think in terms of consolidating those disparate pieces, the variety of recommended health screenings, rather than having multiple different BPAs and notifications, if it pulls them all into one area. I guess the analogy that I'm thinking of is Medicare Wellness Visits is another notification or BPA that comes up. And that includes a number of different elements in terms of recommended screening, immunizations, and testing. And so, rather than pulling all of those different pieces on multiple different screens, having all those different pieces under one kind of smart set, so to speak, I find is user-friendly and helpful.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 09:58</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Yeah, that's great. And this actually does fire for RNs who do&nbsp;annual wellness visits, as well as&nbsp;other providers, which is pretty-- that sounds like it can take the place of some of those BPAs that they receive with the provider.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 10:13</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Yeah.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">H 10:14</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">As a--</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 10:14</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Or if they're appropriately kind of identified in that annual wellness visit, I would think that that would satisfy some of the criteria, so as this Wizard is doing its kind of review and scrubbing, so to speak, then hopefully they wouldn't both need to be firing for the same information.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 10:33</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Right. That's a good point.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">H 10:36</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Yeah. As a nurse practitioner, about how long are your visits typically? Are they 20-minute visits? Or do you have more 40-minute visits?</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 10:43</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Actually, I have 30-minute visits all day.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">H 10:45</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">You have 30-minute visits all day?</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 10:46</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Nice. That's really great.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">H 10:49</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Time with these, during those visits. Someone comes in. How would you, or would you, incorporate these shared decision-making tools?</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 10:59</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">That's very patient-specific, I think. I can't imagine anybody's going to come in to walk through a decision aid to talk about HPV screen, immunization, or lung cancer screening, just that. So I mean, the standard approach or kind of experience that I have on a daily basis is regardless&nbsp;of why they're here, I try to address whatever&nbsp;those screening recommendations are. So if they're here for a blood pressure recheck or a diabetes issue, follow-up, or something like that, "Oh, I notice you're not up-to-date on your mammogram," or whatever the case may be, and then having that conversation in the context of everything else. So I mean, if it's someone who has multiple health issues from cardiovascular, renal, endocrine, thyroid, whatever the case may be, where just getting through the problem list is [laughter] enough of a challenge even in 30 minutes, and then trying to incorporate those health screenings, it is, I guess, more condensed. But I'm still trying to be comprehensive. Again, I can't imagine trying to pluck out one element of lung cancer screening, for example, and saying, "Come back in a week and we'll talk about this entirely separate." I've got them there for that amount of time, so I'm trying to address as much of it as I can. So trying to take another five minutes or more to walk through a decision aid, apart from the counseling and shared decision-making conversation that I'm already having, which, to this point, has felt effective, I can't imagine having a strong motivation to wanting to incorporate another decision aid tool, beyond the shared decision-making conversations I'm already having.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">H 12:56</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Sitting in the patient position as a patient, would you rather have something like this? Or would you rather your provider chat with you about your risk?</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 13:15</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Yeah. I guess I'm having a difficult time putting myself in their shoes. I mean, from the type of-- I guess, having the tool available-- and this is just my own learning preferences and style. Having the tool available to review on my own, I think, would be helpful. If an individual patient wanted to have a separate conversation utilizing a decision aid, I would not throw up a barrier to that in any way.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 13:51</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">So the shared decision-making tools are basically for the providers to use at their discretion. The only one that has any requirement would be the CDC AHRQ. And this is for patients who are on Medicare. The only way Medicare will pay for the low-dose CT scan is if they actually come back and have a separate shared decision-making visit about this. But that's the only time that it would be something to use, so.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 14:18</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Which is different information&nbsp;than what I guess I'd received in the past.&nbsp;I mean, my understanding is that the LDCT had to be ordered initially in the context of an annual wellness visit when a shared decision-making conversation has been had, not as an entirely separate visit.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 14:33</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Okay. Well, that's really good. Okay, then maybe we have the incorrect information, then. So that's good to know.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 14:40</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">So, I mean, that was my understanding of the LDCT for Medicare patients. Now, I mean, the screening, as you know, starts at age 55 before Medicare applies--</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 14:50</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">It does. So, right. For those patients, yeah.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 14:52</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">So then, there's-- I mean, I'm still having that shared decision-making conversation, providing patient information. Anecdotally, I mean, I see my pulmonary colleagues ordering LDCTs for lung cancer screening for people who meet those criteria, regardless of what the visit type is.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 15:10</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Well, that's good. No, that's really good to know. Yeah, because we heard one thing so it's good to find out that that may not be what's happening and practiced because-- yeah.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 15:17</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Yeah.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 15:17</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">So do you think that the shared decision-making tools would help you make a shared decision with your patients?</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 15:27</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I feel like I'd be speaking out of order. I mean, I haven't utilized them formally, over and above-- I mean, I've used the Mayo statin tool with patients, I mean, to give them kind of that visual, kind of population-based atherosclerotic cardiovascular disease ten-year risk kind of image, to pair both the conversation with the visual.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 15:51</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Okay. So let's see. What do you think of the tools, actually? I mean, what are your impressions of them? I know you've talked about using them, but what do you think of them?</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 16:05</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I think they're great. I think they're very helpful in an idealized situation, I mean, for a motivated, activated patient who's interested in kind of receiving that information. And so I can and do make the information available. The extent to which it impacts their decision or our decision together, I mean, varies a great deal. So some people are very hungry for that information and in that situation, I'd be happy to partner with them in that, in providing it and having a conversation. And other folks really aren't at a place where they can comprehend or understand or kind of manipulate that information, or they just aren't interested.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 16:55</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Right. Okay. Yeah, that's true. So right now, the plan is that for half intervention clinics that would get these shared decision-making tools, that they would fire with the BPA for the Wizard. And so they would be handed to the patient-- or the provider, actually. Do you think that's the best way for the patients to receive these, or the best time? Because I guess there's a concern about integrating it into work flow. That's something that other people have brought up. When is the best time for the patients to receive this to have time to review? Do you have any thoughts about that?</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 17:30</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">When is the best time [laughter]?</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 17:32</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Right. Yeah.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">H 17:33</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">In an ideal world.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 17:33</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">An ideal world. Yeah, ideal time.</font></p>
+<p leftindent="26" rightindent="4"></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">[silence]</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">H 17:45</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Like we've had suggestions of in the beginning during the rooming phase, the patients get those so they can look them over. Or they have them prior to the visit through MyHealth. Or they go home and look at them and digest them themselves and then make another appointment.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 18:03</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Afterwards, yeah.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 18:05</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">And the next time they come in--</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 18:09</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">And I see pros and cons in all of those circumstances. I mean, getting the information ahead of time is very out of context and may not be familiar and could even be scary, I mean, if there isn't an opportunity to supplement that with a conversation.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 18:24</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">That's a good point.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 18:25</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Getting that during the rooming process, when they've got other immediate, practical and tangible&nbsp;concerns apart from this information, I think could introduce some cognitive dissonance in terms of distraction, more difficult to address what their priorities are that they're bringing that day. Adding another layer of complexity&nbsp;and consideration when maybe we're adjusting their diabetes&nbsp;or hypertension management. And adherence is such a challenge when, I mean, with the more details and changes that we're already implementing. Taking it home [laughter] afterwards, after trying to process and digest, it may just end up in the waste basket or recycling bin and be barriers to follow-up. So--</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 19:17</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">That's good feedback.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 19:18</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">--I don't think there is one right answer. I mean, we've talked a little bit about the annual wellness visit to this point. And I think a lot of those questions are very practical, day-to-day. So when we send that questionnaire out ahead of time - how many fruits and vegetables, are you physically active, home safety questions, and things like that - that, at this moment, makes sense to me that they would receive that information ahead of time and could kind of walk and process this. Personally, I guess I would be inclined, I suspect, of, if these materials print out because a patient or someone I'm seeing is due for any or all of these, having that material, going through the other&nbsp;stuff, information, and then having that shared decision-making conversation&nbsp;to supplement the decision aids. And then giving them the option to take it home and review it, and then circle back, I guess would probably be the most kind of comfortable&nbsp;and effective approach that I would imagine at this point.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 20:32</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Yeah, that is the one plan for the study. But it could be a possibility later on after, if the intervention is maintained&nbsp;at a center, to do something like send it out, like with the annual wellness visit material. Now, do they email that out to the annual wellness visit patients? Or do they mail it, hand deliver or hand mail that--?</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 20:52</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I'm not familiar with that part of the process.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 20:53</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">No. That's interesting. Yeah, I don't think we've heard about that, that they get anything before having hand, so that's interesting.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 20:59</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I hear about it happening sometimes but not all the time.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 21:02</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">It may not be, okay, consistent. Okay. So how do you currently utilize the CV Wizard print-outs during an office visit?</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 21:11</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">The majority of the time-- well, depending on the chief issue of the visit, I either do or do not use the print-outs. I mean if they're here for a sinus infection, fill in the blank, then I probably will just disregard. If it's for follow up of chronic disease management or annual wellness or something like that, then the majority of the time, we'll go through everything and then use it as a summary tool at the very end. And say, "This is just a way to consolidate information." And then, I mean, I'll provide both sheets to them, explain what the six cardiovascular disease risk factor components are, where they're at in each of those components, trying to prioritize those different elements, trying to make sense out of them. And because we've discussed them earlier in the visit, it's a lot-- it's just kind of reiterating and summarizing. And then gives them something tangible to look at to take with them.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 22:20</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Yeah, that's great. So how do you physically get the handout?</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 22:26</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">During the rooming process, the nurse will fire it and print it off and then in with the rooming form; it's just clipped on the outside of the room.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 22:38</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">So do you ever have a chance to review it before you go in to see your patient? Or do you review it once you're in the room?</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 22:43</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I review it on the fly.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 22:45</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Okay. So how do you document the use of the tool in EPIC, if at all?</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 22:54</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">The print-out, specifically, I don't. I mean, so assuming somebody has impaired fasting glucose prediabetes, dyslipidemia, and hypertension, and they smoke, I mean, my standard documentation is very problem-oriented. So assessment and plan will just incorporate those elements of each of those problems and what we've talked about and any particular treatment or therapy that they're on. But I don't specifically name-- discuss the CV Wizard tool.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 23:30</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Right. Okay. Yeah. And I think that's pretty common not to document it's use. So that wasn't, I don't think, part of the training.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 23:40</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">[laughter] Which I didn't get, anyway.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 23:42</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Which you didn't take, anyways [laughter]. Yeah. So how do you think the integrated Wizard with cancer prevention will affect Essentia&rsquo;s primary care providers and staff in practice?</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 23:59</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I think the intent, and I guess I hope what the outcome would be, is that it will be more overt in terms of bringing forward those kind of regular screening recommendations&nbsp;so that the implementation of those screening recommendations would be more effective, more regular--</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 24:23</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Okay. Yeah.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 24:25</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">--or at least addressed. I mean, I've got a number of patients that, for whatever personal reasons, they do not want to do colorectal cancer screening or mammography. But we've had the conversation and that's been documented. And I mean, a Wizard like this would bring those issues to the fore to at least make sure that they're being addressed and discussed.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 24:45</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">So it sounds like helping to engage the patient?</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 24:47</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Mm-hmm.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 24:49</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Yeah. So do you see any potential disadvantages for providers and staff?</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 24:56</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Yeah. As smart as we make BPAs, they're still dumb. So there are those, I would say, just the frustrating realities of them that a lot of paper, materials, or extra-- where, if in the kind of global health status of that particular patient or again, the reason that they're there for that particular visit, it's just automatically spitting out data and information that may have absolutely no relevance&nbsp;to that particular visit at that particular time. And so I mean, between that and the clicks and how well it's integrated with other BPAs creates the potential for complexity and frustration and ultimately weakening the effectiveness.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 25:46</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Okay. That's a good response. So how do you think it&nbsp;will affect Essentia patients in primary care?</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 25:55</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I&nbsp;think the&nbsp;notifications&nbsp;will help to promote patients receiving information that I think they are eligible for or that we owe to them, as, I mean, evidence-based best practices for clinical decision-making, screening health and wellness. So I think patients would benefit from having consistent notification and awareness&nbsp;of what's available and why.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 26:32</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">So can you see any disadvantages to patients of the tool?</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 26:38</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Just in terms of the--?</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 26:40</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">The Wizard, of the shared decision-making tool. You've talked a bit about this but-- the Wizard, do you see any disadvantages?</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 26:52</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I think in the same way that, I mean, the CV Wizard functions now, coming back visit after visit and getting the print-off, that there's a certain amount of, maybe, psychological burden associated, you know? If you continue&nbsp;to see obesity, obesity, obesity, or, "My cardiovascular risk is whatever because of my tobacco addiction." Where its repeated messaging, true though it may be, is pretty black and white on a Wizard. So I mean, coupling that with hopefully a therapeutic relationship. Not to undermine that but maybe at least mitigate it through a supportive engagement.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 27:38</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">So, kind of one of the principles behind the repeated exposure is to hopefully help change behavior.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 27:45</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Mm-hmm.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 27:45</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Do you think repeated exposure to this for patients may help them increase their likelihood of reducing smoking or addressing--?</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 27:52</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">From a population standpoint? I think in that regard, yeah. I think that would have a statistically significant impact.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 28:00</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Okay.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 28:01</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">But on a--</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 28:01</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">We can hope [laughter].</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 28:02</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Right [laughter]. But on an individual basis, I mean, stress can either mobilize or immobilize.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 28:10</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">That's a very good point. Yeah, that's true. So what triggers you to discuss cancer screening and prevention with your eligible&nbsp;patients?</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 28:19</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">[laughter] My neurotic&nbsp;personality.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 28:21</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Okay [laughter]. Not the BPAs or--?</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 28:25</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">For cancer screening?</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 28:27</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Yeah.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 28:27</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I think the BPAs are helpful. But I mean, in the almost three years of practice to this point, I mean, I've just developed a way to constantly remind myself to circle back and focus on this every visit.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 28:42</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Okay. So you do try to address cancer prevention screening every visit that you have?</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 28:47</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Absolutely, yeah.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 28:47</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Okay. That's great. That's fantastic. So given your understanding and experience at Essentia, what do you feel are major or minor concerns that our research team will need to address to ensure a successful implementation and high utilization of the Wizard?</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 29:06</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I think I mentioned before, just in terms of the design elements and the coordination or flow with other parts of the EMR.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 29:18</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Okay.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 29:19</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Because if it's pulling inaccurate information or there's three BPAs that are firing about the same thing and there's so much overlap, that's going to be a point of frustration and ultimately, people will just wash their hands of it.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 29:34</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Okay. So can you think of any organizational barriers we may face, in addition to alert fatigue?</font></p>
+<p leftindent="26" rightindent="4"></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">[silence]</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 30:01</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Not just organizationally, but in terms of just a-- you had mentioned before some of the discrepancy in kind of recommendations.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 30:16</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Right. Yeah, like for the breast cancer screening--</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 30:18</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Right. I think that's&nbsp;a&nbsp;practical reality that's faced even now with, I mean, recommendations that fire for diabetes and some of those recommendations that-- I mean, cervical cancer screening has changed over the last half a dozen years. Recommendations, breast cancer screenings-- people are still very contentious about LDCT screening and managing incidentalomas and appropriate&nbsp;follow-up.&nbsp;So I mean, I presume and hope that individual providers are finding ways to kind of navigate that in a way that's comfortable and effective for them and their patients. I mean, you've got to draw the line in the sand somewhere, I mean, whether it's in terms of hypertension management or which guidelines, ACOG or USPSTF, or noticing that there's no prostate cancer screening on this tool anywhere.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 31:26</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Yeah, there was some discussion about that.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 31:28</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I would imagine-- yeah, as is appropriate to have the conversation. So I think there's lots of fertile ground for discontent from that perspective, in that there is no unanimous consent&nbsp;or decision.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 31:48</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Right. Yeah, we have gotten some feedback that if a provider doesn't necessarily agree with one of the recommendations, they may just not want to use the entire Wizard. So that is a concern. We do want to make sure that providers know-- I mean, it is, again, up to your discretion to use, too, so.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 32:06</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">And we had talked a little bit before, as well, about some of the criteria that are involved in some of those cancer screening recommendations, I mean, namely the LDCT and frequency in terms of Pap smears. I mean, is the Wizard able to make a distinction between family history or previous abnormal Pap smears? I mean, there's a level of kind of clinical specificity there that demands more-- as I said, as smart as we make a BPA, it can only be so smart.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 32:39</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">So that's a good point. Yeah. So hopefully the cervical cancer BPA-- or the algorithm in the Wizard, I should say, will go and look at the family health history and document-- or previous history to see if there had been atypical cells&nbsp;or something, so. Yeah, so--</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 32:54</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Right. Which I'd be surprised at. I mean, the way that the pathology reports are implemented and utilized, you don't necessarily always see a health history or problem list that's updated to reflect that effectively.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 33:06</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">That's good feedback. Right. Okay. So there may be some, I would say inaccuracy. But the EMR may be kind of hard to scrub for some of those things?</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 33:19</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Absolutely.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 33:21</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Okay. So what do you think about ensuring a seamless implementation and high utilization? What could we do to increase the likelihood of both of those things with Essentia&nbsp;patients?</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 33:36</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">[inaudible].</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 33:36</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Do you want me to rephrase it?</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 33:37</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Yeah, please.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 33:38</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">So what do you think we could do to encourage use of the Wizard with patients at Essentia?</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 33:44</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">[laughter] The cynic&nbsp;in me would-- pay for performance.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 33:55</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Okay.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 33:56</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Garnishing wages for people who don't utilize it [laughter], but that probably would not go over so well.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 34:01</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">No.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 34:08</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Is there kind of a conceptual framework, I would assume, underlying kind of implementation to this point? I mean, I guess I would presume I'm part of it in terms of, I mean, just getting information--</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 34:22</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Yes. Yeah.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 34:23</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">--to this point in developing, trying to identify, I mean, well, stakeholders, I mean, barriers, and opportunities for progression, so.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 34:32</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Right. Yep. Barriers and facilitators. Exactly. Yeah.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 34:34</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Yeah.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 34:35</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Yeah.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 34:37</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">And so I would feel a little presumptuous [laughter] trying to offer a clear vision of how to implement something that you're implementing.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 34:48</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Okay. That's okay. So is there any questions that I didn't ask today, comments that you have or concerns, maybe, that you'd like to talk about?</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 35:02</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">No. I think we've addressed-- I think I've had an opportunity to kind of give voice to some of the potential gaps and barriers--</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 35:13</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Which is great.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 35:14</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">--and pros and cons, so.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">H 35:15</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Yeah. We really appreciate it.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 35:17</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Yeah. We really do. Yeah. We need those things. We need to know what's going on on the ground and how the CV Wizard is currently being used and--</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">H 35:24</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Or not being used.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 35:24</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Or not being used [laughter]. Yeah. Because this will add extra layers to it. So we want to make it a tool that providers want to use, as opposed to never use.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">H 35:35</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Burden.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 35:35</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Right, or a burden. Same with patients, too.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 35:37</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Yep. And realistic aspirations. I mean, from a design team, I mean it&rsquo;s --, and even from a research study, it's your-- I mean, you've got a personal stake, invested interest in the success of this, I presume. I apologize if I'm projecting&nbsp;inappropriately, but I think you'd want it to be successful.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 35:58</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">We'd hope, right.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 35:58</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">But I think managing realistic expectations in terms of-- I wouldn't anticipate that there's going to be a universal panacea that's going to address all of these things for every patient. So--</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 36:08</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Exactly.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 36:09</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">--approaching it from a population perspective where we're moving the bar a little bit, I mean, it does seem to be an appropriate aspiration.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 36:17</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Right.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">H 36:18</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Great.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 36:19</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Thank you.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">H 36:20</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Thank you so much.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 36:21</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Yeah. This was an excellent interview. Would you like to continue being updated on the project as it goes forward and--?</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 36:28</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">It sounds like I'll be hearing about it coming up in January.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">H 36:31</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">In January.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 36:32</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Yeah.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">H 36:33</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Probably before then.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 36:33</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Before then we'll do--</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">H 36:34</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Hopefully you'll get training this time [laughter].</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 36:35</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Yes.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">I 36:37</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Hopefully I haven't suffered too much as a result of not getting training on the CV Wizard.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">H 36:41</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">No.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 36:42</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Right.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">H 36:42</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">No. You seem to know what's going on pretty well.</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">M 36:44</font></p>
+<p leftindent="26" rightindent="4" spaceabove="4" spacebelow="4"><font face="Arial" size="12">Yes. Definitely. Yeah.</font></p>
+<p></p>
+<p>__________</p>
+<p>__________</p>
diff --git a/tests/lcs/core/field/pageHeights.livecodescript b/tests/lcs/core/field/pageHeights.livecodescript
new file mode 100644
index 00000000000..26b5d3208db
--- /dev/null
+++ b/tests/lcs/core/field/pageHeights.livecodescript
@@ -0,0 +1,50 @@
+script "CoreFieldPageHeights"
+/*
+Copyright (C) 2018 LiveCode Ltd.
+
+This file is part of LiveCode.
+
+LiveCode is free software; you can redistribute it and/or modify it under
+the terms of the GNU General Public License v3 as published by the Free
+Software Foundation.
+
+LiveCode is distributed in the hope that it will be useful, but WITHOUT ANY
+WARRANTY; without even the implied warranty of MERCHANTABILITY or
+FITNESS FOR A PARTICULAR PURPOSE.  See the GNU General Public License
+for more details.
+
+You should have received a copy of the GNU General Public License
+along with LiveCode.  If not see <http://www.gnu.org/licenses/>.  */
+
+on TestPageHeights
+    
+   open this stack
+   create field "testPageHeightsField" 
+   
+   // Recreate field similar to the one of the attached stack to bug 21491
+   set the textFont of field "testPageHeightsField" to "Segoe UI"
+   set the textSize of field "testPageHeightsField" to 13
+   set the textAlign of field "testPageHeightsField" to "left"
+   set the fixedLineHeight of field "testPageHeightsField" to true
+   set the borderwidth of field "testPageHeightsField" to 0
+   set the margins of field "testPageHeightsField" to 6
+   set the width of field "testPageHeightsField" to 474
+   set the height of field "testPageHeightsField" to 692 
+   
+   local tFieldContentFilename
+   set the itemDel to slash
+   put item 1 to -2 of the filename of this stack into tFieldContentFilename
+   put slash & "_pageHeightsFieldContent.txt" after tFieldContentFilename
+   set the htmlText of field "testPageHeightsField" to url ("file:/"&tFieldContentFilename)
+   
+   TestAssert "Field is not empty", field "testPageHeightsField" is not empty
+      
+   local tObservedPageHeights
+   put the pageHeights of field "testPageHeightsField" into tObservedPageHeights
+      
+   TestAssert "pageHeights is not empty", tObservedPageHeights is not empty
+   
+   TestAssert "The number of lines of the pageheights is 24", the number of lines of tObservedPageHeights is 24
+   delete field 1
+    
+end TestPageHeights