An anchoring device used with a percutaneous catheter/tube (e.g., suprapubic tube, nephrostomy tube) is billed using code A5200. Just shove the raw code into a listing block. Your document now has a title, but what about an author? Description lists are quite lenient about whitespace, so you can spread the items out and even indent the content if that makes it more readable for you: Finally, you can mix and match the three list types within a single hybrid list. Instinct might tell you to prefix each item with a number, like in this next list: The above works, but Stored source text of PL/SQL units. It allows for the parallel development of classes due to which object oriented programming is considered as a quickest way of development for completing the programs. Value MUST be equal to or greater than 0. In those cases, youll need to use markup to escape the text. ), PER OZ, OSTOMY SKIN BARRIER, SOLID 4 X 4 OR EQUIVALENT, STANDARD WEAR, WITH BUILT-IN CONVEXITY, EACH, OSTOMY SKIN BARRIER, WITH FLANGE (SOLID, FLEXIBLE OR ACCORDION), WITH BUILT-IN CONVEXITY, ANY SIZE, EACH, OSTOMY POUCH, DRAINABLE, WITH FACEPLATE ATTACHED, PLASTIC, EACH, OSTOMY POUCH, DRAINABLE, WITH FACEPLATE ATTACHED, RUBBER, EACH, OSTOMY POUCH, DRAINABLE, FOR USE ON FACEPLATE, PLASTIC, EACH, OSTOMY POUCH, DRAINABLE, FOR USE ON FACEPLATE, RUBBER, EACH, OSTOMY POUCH, URINARY, WITH FACEPLATE ATTACHED, PLASTIC, EACH, OSTOMY POUCH, URINARY, WITH FACEPLATE ATTACHED, RUBBER, EACH, OSTOMY POUCH, URINARY, FOR USE ON FACEPLATE, PLASTIC, EACH, OSTOMY POUCH, URINARY, FOR USE ON FACEPLATE, HEAVY PLASTIC, EACH, OSTOMY POUCH, URINARY, FOR USE ON FACEPLATE, RUBBER, EACH, OSTOMY FACEPLATE EQUIVALENT, SILICONE RING, EACH, OSTOMY SKIN BARRIER, SOLID 4 X 4 OR EQUIVALENT, EXTENDED WEAR, WITHOUT BUILT-IN CONVEXITY, EACH, OSTOMY POUCH, CLOSED, WITH BARRIER ATTACHED, WITH BUILT-IN CONVEXITY (1 PIECE), EACH, OSTOMY POUCH, DRAINABLE, WITH EXTENDED WEAR BARRIER ATTACHED, (1 PIECE), EACH, OSTOMY POUCH, DRAINABLE, WITH BARRIER ATTACHED, WITH BUILT-IN CONVEXITY (1 PIECE), EACH, OSTOMY POUCH, DRAINABLE, WITH EXTENDED WEAR BARRIER ATTACHED, WITH BUILT-IN CONVEXITY (1 PIECE), EACH, OSTOMY POUCH, URINARY, WITH EXTENDED WEAR BARRIER ATTACHED (1 PIECE), EACH, OSTOMY POUCH, URINARY, WITH STANDARD WEAR BARRIER ATTACHED, WITH BUILT-IN CONVEXITY (1 PIECE), EACH, OSTOMY POUCH, URINARY, WITH EXTENDED WEAR BARRIER ATTACHED, WITH BUILT-IN CONVEXITY (1 PIECE), EACH, OSTOMY DEODORANT, WITH OR WITHOUT LUBRICANT, FOR USE IN OSTOMY POUCH, PER FLUID OUNCE, OSTOMY DEODORANT FOR USE IN OSTOMY POUCH, SOLID, PER TABLET, OSTOMY BELT WITH PERISTOMAL HERNIA SUPPORT, OSTOMY IRRIGATION SUPPLY; CONE/CATHETER, WITH OR WITHOUT BRUSH, OSTOMY SKIN BARRIER, NON-PECTIN BASED, PASTE, PER OUNCE, OSTOMY SKIN BARRIER, PECTIN-BASED, PASTE, PER OUNCE, OSTOMY SKIN BARRIER, WITH FLANGE (SOLID, FLEXIBLE, OR ACCORDION), EXTENDED WEAR, WITH BUILT-IN CONVEXITY, 4 X 4 INCHES OR SMALLER, EACH, OSTOMY SKIN BARRIER, WITH FLANGE (SOLID, FLEXIBLE OR ACCORDION), EXTENDED WEAR, WITH BUILT-IN CONVEXITY, LARGER THAN 4 X 4 INCHES, EACH, OSTOMY SKIN BARRIER, WITH FLANGE (SOLID, FLEXIBLE OR ACCORDION), EXTENDED WEAR, WITHOUT BUILT-IN CONVEXITY, 4 X 4 INCHES OR SMALLER, EACH, OSTOMY SKIN BARRIER, WITH FLANGE (SOLID, FLEXIBLE OR ACCORDION), EXTENDED WEAR, WITHOUT BUILT-IN CONVEXITY, LARGER THAN 4 X 4 INCHES, EACH, OSTOMY SKIN BARRIER, SOLID 4 X 4 OR EQUIVALENT, EXTENDED WEAR, WITH BUILT-IN CONVEXITY, EACH, OSTOMY POUCH, DRAINABLE, HIGH OUTPUT, FOR USE ON A BARRIER WITH FLANGE (2 PIECE SYSTEM), WITHOUT FILTER, EACH, OSTOMY POUCH, DRAINABLE, HIGH OUTPUT, FOR USE ON A BARRIER WITH FLANGE (2 PIECE SYSTEM), WITH FILTER, EACH, OSTOMY SKIN BARRIER, WITH FLANGE (SOLID, FLEXIBLE OR ACCORDION), WITHOUT BUILT-IN CONVEXITY, 4 X 4 INCHES OR SMALLER, EACH, OSTOMY SKIN BARRIER, WITH FLANGE (SOLID, FLEXIBLE OR ACCORDION), WITHOUT BUILT-IN CONVEXITY, LARGER THAN 4 X 4 INCHES, EACH, OSTOMY POUCH, CLOSED, WITH BARRIER ATTACHED, WITH FILTER (1 PIECE), EACH, OSTOMY POUCH, CLOSED, WITH BARRIER ATTACHED, WITH BUILT-IN CONVEXITY, WITH FILTER (1 PIECE), EACH, OSTOMY POUCH, CLOSED; WITHOUT BARRIER ATTACHED, WITH FILTER (1 PIECE), EACH, OSTOMY POUCH, CLOSED; FOR USE ON BARRIER WITH NON-LOCKING FLANGE, WITH FILTER (2 PIECE), EACH, OSTOMY POUCH, CLOSED; FOR USE ON BARRIER WITH LOCKING FLANGE (2 PIECE), EACH, OSTOMY ABSORBENT MATERIAL (SHEET/PAD/CRYSTAL PACKET) FOR USE IN OSTOMY POUCH TO THICKEN LIQUID STOMAL OUTPUT, EACH, OSTOMY POUCH, CLOSED; FOR USE ON BARRIER WITH LOCKING FLANGE, WITH FILTER (2 PIECE), EACH, OSTOMY POUCH, DRAINABLE, WITH BARRIER ATTACHED, WITH FILTER (1 PIECE), EACH, OSTOMY POUCH, DRAINABLE; FOR USE ON BARRIER WITH NON-LOCKING FLANGE, WITH FILTER (2 PIECE SYSTEM), EACH, OSTOMY POUCH, DRAINABLE; FOR USE ON BARRIER WITH LOCKING FLANGE (2 PIECE SYSTEM), EACH, OSTOMY POUCH, DRAINABLE; FOR USE ON BARRIER WITH LOCKING FLANGE, WITH FILTER (2 PIECE SYSTEM), EACH, OSTOMY POUCH, URINARY, WITH EXTENDED WEAR BARRIER ATTACHED, WITH FAUCET-TYPE TAP WITH VALVE (1 PIECE), EACH, OSTOMY POUCH, URINARY, WITH BARRIER ATTACHED, WITH BUILT-IN CONVEXITY, WITH FAUCET-TYPE TAP WITH VALVE (1 PIECE), EACH, OSTOMY POUCH, URINARY, WITH EXTENDED WEAR BARRIER ATTACHED, WITH BUILT-IN CONVEXITY, WITH FAUCET-TYPE TAP WITH VALVE (1 PIECE), EACH, OSTOMY POUCH, URINARY; WITH BARRIER ATTACHED, WITH FAUCET-TYPE TAP WITH VALVE (1 PIECE), EACH, OSTOMY POUCH, URINARY; FOR USE ON BARRIER WITH NON-LOCKING FLANGE, WITH FAUCET-TYPE TAP WITH VALVE (2 PIECE), EACH, OSTOMY POUCH, URINARY; FOR USE ON BARRIER WITH LOCKING FLANGE (2 PIECE), EACH, OSTOMY POUCH, URINARY; FOR USE ON BARRIER WITH LOCKING FLANGE, WITH FAUCET-TYPE TAP WITH VALVE (2 PIECE), EACH, OSTOMY POUCH, DRAINABLE, HIGH OUTPUT, WITH EXTENDED WEAR BARRIER (ONE-PIECE SYSTEM), WITH OR WITHOUT FILTER, EACH, IRRIGATION SUPPLY; SLEEVE, REUSABLE, PER MONTH, IRRIGATION SUPPLY; SLEEVE, DISPOSABLE, PER MONTH, TAPE, NON-WATERPROOF, PER 18 SQUARE INCHES, ADHESIVE REMOVER OR SOLVENT (FOR TAPE, CEMENT OR OTHER ADHESIVE), PER OUNCE, OSTOMY POUCH, CLOSED; WITH BARRIER ATTACHED (1 PIECE), EACH, OSTOMY POUCH, CLOSED; WITHOUT BARRIER ATTACHED (1 PIECE), EACH, OSTOMY POUCH, CLOSED; FOR USE ON FACEPLATE, EACH, OSTOMY POUCH, CLOSED; FOR USE ON BARRIER WITH FLANGE (2 PIECE), EACH, OSTOMY POUCH, DRAINABLE, WITH EXTENDED WEAR BARRIER ATTACHED, WITH FILTER, (1 PIECE), EACH, OSTOMY POUCH, DRAINABLE, WITH EXTENDED WEAR BARRIER ATTACHED, WITH BUILT IN CONVEXITY, WITH FILTER, (1 PIECE), EACH, OSTOMY POUCH, DRAINABLE; WITH BARRIER ATTACHED, (1 PIECE), EACH, OSTOMY POUCH, DRAINABLE; WITHOUT BARRIER ATTACHED (1 PIECE), EACH, OSTOMY POUCH, DRAINABLE; FOR USE ON BARRIER WITH FLANGE (2 PIECE SYSTEM), EACH, OSTOMY POUCH, URINARY; WITH BARRIER ATTACHED (1 PIECE), EACH, OSTOMY POUCH, URINARY; WITHOUT BARRIER ATTACHED (1 PIECE), EACH, OSTOMY POUCH, URINARY; FOR USE ON BARRIER WITH FLANGE (2 PIECE), EACH, CONTINENT DEVICE; CATHETER FOR CONTINENT STOMA, CONTINENT DEVICE, STOMA ABSORPTIVE COVER FOR CONTINENT STOMA, BEDSIDE DRAINAGE BOTTLE WITH OR WITHOUT TUBING, RIGID OR EXPANDABLE, EACH, SKIN BARRIER; SOLID, 6 X 6 OR EQUIVALENT, EACH, SKIN BARRIER; SOLID, 8 X 8 OR EQUIVALENT, EACH, ADHESIVE OR NON-ADHESIVE; DISK OR FOAM PAD. In this example of an Array definition, a "documentation" Property key has an Array value that contains two Objects: In the merging algorithm, the Property types are referred to as Property Kind, which can be one of the following properties highlighted in bold: Object Property - a Property having Object as a value. An alternate, human-friendly name for the example. Its your call afterall. In order to be coded as A4353, a no-touch type of catheter system must be a sterile, all-inclusive, self-contained system capable of accomplishing intermittent catheterization with sterile technique without the use of additional supplies such as gloves, lubricant, collection chamber, etc. No other changes have been made to the Articles. CMS WILL NOT BE LIABLE FOR ANY CLAIMS ATTRIBUTABLE TO ANY ERRORS, OMISSIONS, OR OTHER INACCURACIES IN THE INFORMATION OR MATERIAL CONTAINED ON THIS PAGE. and/or making any commercial use of UB‐04 Manual or any portion thereof, including the codes and/or descriptions, is only The data-ui-components value can take any format you wish, like title case: Each item in a description list consists of: a separator following each term (typically a double colon, ::), the supporting content (either text, attached blocks, or both). A C with a hyphen is placed afterwards, as the identification symbol for casting alloys e.g. Imagine a more complex example: A union type MAY use facets defined by any of its member types as long as all member types in the union accept those facets, for example: RAML allows the use of XML and JSON schemas to describe the body of an API request or response by integrating the schemas into its data type system. If all of the applicable R&N criteria in the COVERAGE INDICATIONS, LIMITATIONS AND/OR MEDICAL NECESSITY section in the related LCD have not been met, a GA or GZ modifier must be added to the code. Heres a simple example of a table with two columns and three rows: The first non-blank line inside the block delimiter (|===) determines the number of columns. The value of this node MUST be a map where key names become names of traits that MAY be referenced throughout the API, and values are trait declarations. The output will be sorted according to the current locale and displayed in a reusable format. Naming things correctly in CSS will make your code easier to read and maintain. Some blocks can masquerade as other blocks, a feature which is controlled by the block style. Although a URI parameter MAY be explicitly specified as optional, it SHOULD be required when surrounded directly by slashes (/). Processors can then rely on the declarations to ensure annotation values meet expectations. This section describes how an API designer MAY include security scheme definitions in RAML API definitions. Mutually exclusive with. The tag is used for specifying subtitles. The name of the file should not contain two consecutive underscore characters. since the numbering is obvious, the AsciiDoc processor will insert the numbers for you if you omit them: If you decide to use number for your ordered list, you have to keep them sequential. The following example illustrates a very simple RAML definition of a library books API, along with overlay files that provide a Spanish translation and metadata for an API monitoring service. Its value is a string. Reg Vol 217) that do not meet the face-to-face encounter and WOPD requirements specified in the LCD-related Standard Documentation Requirements Article (A55426) will be denied as not reasonable and necessary. If you were to create a list in an e-mail, how would you do it? Properties defined in both method node and trait node (including optional ones) are treated as follows: Collection properties are merged by value, as described later. You do not need to specify the media type within every body definition. WebSingle-instance component names #. You can collapse such groups by clicking on the group header to make navigation easier. This document constitutes the RAML 1.0 specification. CMS DISCLAIMS RESPONSIBILITY FOR ANY LIABILITY ATTRIBUTABLE TO END USER USE OF THE CPT. If you do not agree with all terms and conditions set forth herein, click below on the button labeled "I do not accept" and exit from this computer screen. Heres an example of a description list that identifies parts of a computer: By default, the content of each item is displayed below the description when rendered. It is typically applied as a child of the